Commander Very Slow After Upgrade To V10.1 Sr1 S’abonner

0
Avatar
Legacy Poster

I have Commander installed on my server to process some labels. the speed was fine before upgrading from ver. 8 to 10.1 SR1.

 

I get a message on Commander saying : Bartender is still processing the last command. Upgrading Commander and increasing the number of processes could result in a performance increase.

 

How to increase the processes ?

 

Attachment is the configuration..

 

It takes between 20sec- 30 sec to print one label after other.

 

My commander is running as service

 

 

 

8 commentaires

0
Avatar
Fernando Ramos Miracle
Modérateur
Actions pour les commentaires Permalien

Hello,

 

Could you let me what edition of BarTender are you working with? In order to increase the number of processes per BarTender command handler you'll need the Enterprise Automation edition.

 

The number of processes are set in the "Detection>BarTender Command Handler Setup..." dialog, under the "General" tab. Simply select the handler in use by your Commander task and increase its number of processes. This way the handler will be able to deal with several print jobs at the same time, instead of having them wait in queue.

 

Cheers.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

We also have the same issue on slow printing using Commander.

We are using 9.4 SR3.

We used to have a decent printing time but now it is slow since we upgraded our license from 10 to 20.

It is the same label and the same script we used but we are experiencing delay from the time the CSV gets converted to DAT, till the data displays on the print queue.

About 40-60 seconds.

Here is the sample script:

%BTW% /AF="\\Vxxxx01\Bartender\Inventory\ThisLabel.btw" /PRN="\\Vyyyy01.country.local\VyyyyPrn09" /R=3 /D="%Trigger File Name%" /C=1 /P 
%END%
Company, Serial, PartNum, LotNum, Quantity, UOM, Warehse, Bin, MfgLot, MfgDate, ExpDate, NetWt, GrossWt
"VXX","20131220.0061","VX123456701","79996","2500","PC","MAIN","BIN","79996","27/Nov/2013","","0","0"

 

All printers are wireless.

The folder "\\Vxxxx01\Bartender\Inventory\"  is local, printers are in another country.

But we change the Commander service as an Application, this same file only takes about 3-5 seconds.

 

Why is it faster to print when running Commander as an application? What settings do we need?

 

Thank you,

artn

 

 

0
Avatar
Fernando Ramos Miracle
Modérateur
Actions pour les commentaires Permalien

Hello Arthurnito,

 

If as a service is slow, but as an application is running correctly, you might be suffering of some sort of permissions issue.

 

Could you try changing the user account under which the Commander service is running to one with enough access rights (as a first test you should use the one you were working with when running Commander as an application).

 

Also, please make sure to enter the "Detection>BarTender Command Handler Setup..." option and, under the "User Account" tab remove any credentials you've set there and uncheck the "Run BarTender under specified account" option.

 

Note that the BarTender command handler will inherit its credentials from the Commander service, so unless you wish the service and the handler to run under different accounts you shouldn't specify any for the latter.

 

Does the above help improve your issue?

 

Regards.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Thank you Fernando.

We did change the user running Commander as a member of the admin group. There is no specified account in Bartender.

It is still slow. The alert would say the document was sent to the printer but the print queue is still empty. After 20-30 secs., the print queue would say spooling for awhile then printing. That is another 10-20 secs. Total time is somewhere 40-60 secs.

 

Arthur

0
Avatar
Fernando Ramos Miracle
Modérateur
Actions pour les commentaires Permalien

Hello Arthurnito,

 

Could it be that your print jobs are quite heavy (a lot of graphic data from images, TrueType fonts...)? If this is the case, it might be that the memory that the BarTender process is using when Commander is working as a service is not enough, causing the print job to be slow or even to crash.

 

Please access the "Detection>BarTender Command Handler Setup..." dialog and, under the "Advanced" tab, increase the desktop heap memory per process (maybe to 1024Mb). Do you get a better result when doing this?

 

Regards.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Hi Fernando,

 

Our labels are simple, one small logo, mostly texts and bar codes. We use the Code39 Full ASCII for the bar codes, and standard fonts (Arial, MS Sans Serif). Bit I will try your suggestion.

 

Thanks, Arthur

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Hi Fernando,

 

One of your support has implemented some change:

~ Polling Interval from Immediate to Polling 1000 secs

~ Desktop Heap from Shared to Separate - 1024 KB

 

We'll see if this improves the process.

 

Thanks,

Arthur

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Check out BarTender 2016 and the new Integrations Platform: http://www.seagullscientific.com/label-software/barcode-label-design-and-printing/

Vous devez vous connecter pour laisser un commentaire.