Has anyone has this similar experience.
In my experience, Count Tags run reasonably fast UNLESS there’s any kind of issue with the record, then it’s REALLY slow. 60+ records per minute for valid records, but 15 seconds+ for any rows with an error.
We experienced this in the middle of our full physical inventory. The level of panic that set in when I realized that the RPM was in the single digits no matter where I ran it, and thousands of tags still needed to be loaded is hard to describe. Support was less than helpful. We ended up grabbing 10 extra laptops and got them all loading tags to catch up.
The response I got was around the DMT client and the new, 64 bit one would be faster as it could use more local resources for processing. Our analysis of the issue showed that the method for entering count tags ran ~40 queries for each tag being loaded, so while the DMT client may be faster there still seems to be some inefficiency within the method itself.
IF we ever run a full physical again, I have some ideas on a modified entry screen that would help get the tags entered when the user scans versus them scanning into a spreadsheet that we load. I really hope I never have to go through that again though.