Commander Performance Expectations 追蹤

0
Avatar
Legacy Poster

I have a commander task up and running using a TCP/IP trigger and receiving commands via BTXML.  I've been tweaking the various service and detection settings, but regardless of the configuration, the round trip for a single execution generating a single label takes about 2.7 seconds.  The system is not constrained by CPU or memory while the process is executing.  I have attached the BTXML.

 

As it is, that's far too slow for our needs.  Should I expect better results?  What settings should be modified?

3 意見

0
Avatar
Shotaro Ito
評論操作 永久連結

As it is, that's far too slow for our needs.  Should I expect better results?  What settings should be modified?

Do you retrieve preview image from another server with this trigger?

 

Receive TCP IP socket, 

save the trigger, 

load the document, 

apply database,

create preview image, 

save the image,

encode image to xml,

return response

 

... above would take some time. It might takes some time in first document load, would running the same trigger 2nd time make faster?

try with lower resolution export image, simple document etc.

by Reading xml response, print job log, preview timestamp etc, try to identify which part takes the most of time.
0
Avatar
Legacy Poster
評論操作 永久連結

... above would take some time. It might takes some time in first document load, would running the same trigger 2nd time make faster?

 

Is there a method (commander, .net, com, etc.) that would be noticeably faster?

0
Avatar
Shotaro Ito
評論操作 永久連結

Processing time would be depends on what do you print rather than which integration method, and all methods (Commander, .net SDK and ActiveX COM) launches and controls BarTender internally to perform print, so there's not big difference. Being said that, I would bet Commander would have chance to be the fastest, as it has integrated performance options like multiple process handling and format cache.

登入寫評論。