[WD17] iZoneHeight very slow

Startbeitrag von David Egan am 03.12.2014 06:51

At one particular site, the users have been complaining about how long it takes to finalise a sale. Running the profiler across it we can see that iZoneHeight, which we've been using for years to calculate the space required for printing the header section on the sales docket, is taking approx 9 seconds to run (they reckon it has taken up to 3 minutes but we haven't seen anything that suggests that amount of time). Once it gets past this though everything happens in milliseconds, as you'd expect. The site is using Epson TM T82ii printers, running through the Epson APD. By default our docket uses Arial but we've tried changing the font and this hasn't helped.

Because this is an internal Windev command I'm at a bit of a loss as to what it could be. At this same site we had problems with iEscape (which we use to trigger the cash drawer) also being very slow but we can work around that by setting it in the printer driver. We have plenty of sites running identical versions of the software with all sorts of printers including various Epsons (maybe not the same model though) without any issues. My gut feeling is that it is driver related but they do have the latest drivers installed.

We also use iZoneHeight in a couple of other parts of the docket but there is no problem with them. We do call it in the header before we print anything; could this have any bearing on it?

Any thoughts or suggestions would be greatly appreciated.




Hi David

2 facts look interesting to me:

- From what you are telling us, it seems that the problem is on the FIRST printing function (or at least the first one that needs to talk to the driver/printer to get information about size and stuff), which you can verify by putting another function before izoneheight and redo your test.

- Also the variable delay looks like something is waking up...

So I would think that the problem is that the printer is in some kind of sleep mode (energy saving or such wonderful nonsense), and that the printer is trying desperately to wake it before answering the report request to know stuff (page height depending of the paper used, maybe?)...

If that is the case, it would explain the different delays (printer is busy cleaning up, asleep, etc) and modifying its settings so that it's ALWAYS ready may solve the problem.

Also, make sure that the driver are EPSON latests (those coming from windows update are generally months old)...

Best regards

von Fabrice Harari - am 03.12.2014 10:16
Thanks Fabrice
You may have just hit the nail on the head! Be nice if it is that simple & I can honestly say that I hadn't given that a thought.



von David Egan - am 05.12.2014 19:14
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.