Web Service takes 10s to start printing the label
Hi,
I'm in the trial period of Bartender.
I have created a REST Webservice for printing a label. Looks good, but when I call it, it needs almost 10 seconds to print the label. This is too long! The print job needs to start at most 1s after I call the web service.
How can I solve this?
If not solved, I need a different Software.
BR
Michael Hoeller
-
Hi Andy,
I tried suggestions from Xabier, but they did not help in my case.
I contacted the support, who had a good suggestion: Don't use "Inherit user credentials" option for the integration, instead "Spedify user credentials". This brought the delay from 10 seconds down to 3 seconds to send the job to the printer spooler. Not optimum, because a user always needs to wait 3 seconds + printing time, but one step closer to good solution.
Still waiting for the support to get the last 3 seconds down.
1 -
Hello Michael,
Welcome to the BarTender Community Forums!Performance issues can be difficult to troubleshoot, especially through our forums. There could be several factors contributing to this delay, ranging from network latency to the configuration of your printing setup, that is why we would recommend reaching us directly via our Get Support page. That being said, here are some steps you can take to try and solve this issue:
- Optimize Web Service: Ensure that your REST web service is optimized for performance. Check if there are any bottlenecks in the code that could be causing delays. Profile your code to identify areas that might need optimization.
- Server Resources: Make sure the server running your web service has sufficient resources (CPU, memory, etc.) to handle the load. If the server is overloaded, it could lead to delays in processing requests.
- Network Latency: Check the network latency between the client sending the request and the server. High network latency can contribute to delays in communication. If possible, consider hosting your web service on a server closer to your printing device or implementing a content delivery network (CDN).
- Printer Configuration: Check the configuration of your printer. Some printers might have settings that cause delays in processing print jobs. Look for options related to spooling, buffer size, or print job processing speed.
- Print Driver: Ensure that you have the latest print driver installed for your printer. Outdated or incompatible drivers could lead to delays in printing. Also, use our dedicated Drivers by Seagull™ printer drivers if possible.
- Parallel Processing: If you're sending multiple print jobs, consider implementing parallel processing on the server side. This can help distribute the workload and reduce the overall processing time.
- Print Server: If your printing process involves multiple steps, consider setting up a dedicated print server that can handle the printing tasks separately from the web service. This can help offload the processing load from your main web server.
I hope this helps!
0 -
Hi Xabier, those suggestions seem like they are are all from before the Bartender REST API was an option. Almost all of those items don't or shouldn't apply with Bartenders REST API...
0 -
Thanks for the update Michael! In a high speed production process, that 3sec matters and needs to be taken into account. There's always going to be a tiny bit of lag due to network but question then is if that delay is actually internal to the printer and how long it takes to action a new job.
0 -
Hi Andy,
it still needs 2-3 seconds to send the print job to the spooler. I also tried this with connecting the printer directly to the PC (USB or ethernet cable), but this did not help.
I also observed this:
1. when I print the same label from the Bartender Designer, then the printer starts immediately (within a few milliseconds)
2. when I print a less "complex" document (2 instead of 10 fields, no QR code), then the printer starts within 1 second
With my 2nd observation, it is strange that a slightly more "complex" document with a QR code really takes it 2 seconds longer to generate it?! I think this cannot be a MUCH more demanding task computationally.
0
Please sign in to leave a comment.
Comments
5 comments