A client is dependent on the History | Items function to look up sales info about customers and items.

Yesterday, it took about 10 seconds after clicking Load to generate the transactions (they have a ton of history). Today, using the same selection criteria, it took a couple of minutes. This happened on multiple machines (we tried three), using a variety of XP and Win7 systems.

I'm not sure where to start troubleshooting this. What matters most to the Load speed? What could have changed overnight?

Thanks

Steve

It's possible that the anti-virus is checking the file when it's first opened. Also, the file is not very volatile, and so more and more of it will be cached in memory as inquiries are done. Also, it given the wide variation in the times, perhaps Windows is running out of memory and starts paging applications to disk. Look specifically for Outlook, and ask the order that the applications are loaded. Outlook grabs all the memory it can when it starts, there may be little left over for Adagio.

Perhaps it's time to purge some of that history?

Purging the history is not an option. Especially since the lookup was fast yesterday.

The fact that the change happened on multiple workstations seems to rule out local RAM on a particular computer. What memory are you referring to?

Steve

Steve,
The order of the fields you are selecting can be important.
You should always have the smallest selection first.
ie: If searching for a specific item then Item should be first.
If searching for a customer over many items that should be first.
The other thing to watch is if you are searching all dates or in a specific time period.

Can you tell us the ranges and order of the ranges that you have selected?

Hi Chris

I have done a lot of testing on this, and I think I nailed it.

When I pick a customer range BREE40 to BREE40, item range DABAR4620 to DABAR4620, for YTD, it takes about 1 minute to search and finds three matches, which is correct. It's the same no matter whether I make the item number or the customer first.

When I do nothing else but change the ending item number to DABAR4621 (there is no such number), it takes 5 seconds. Still finds the same three matches.

When I do nothing else but change the ending customer to BREE41 (there is no such customer), it still takes about 1 minute. Still finds the same three matches.

So there's something about picking a single item that slows the system down tremendously.

This is on my standalone Win7 PC.

If you would like the data (it's large), I'll upload it to you, let me know.

Steve

Hi Steve,

This is just postulation, but there was something addresed in a recent OE hot fix and it was in the current Service pack for 8.1E 2013.03.22; this is the very first in the 'problems fixed' list:

The Load History function on the Items tab in Display History displayed incorrect results in some cases when you had a range of
customers, items and dates, did a search, then changed fields in the range.

Perhaps the change to ensure that the correct results were loaded in some cases (such as a single item number) doesn't use the available indexes for fast searching in the most efficient manner.

Hi Softrak

I am using the 130402 hotfix.

Your reply implies that you will be following up on this. You are not asking me do anything at the moment, correct?

Steve

My quick test running OrderEntry 8.1E and the current service pack had the item history inquiry find transactions for a single specific item and customer (no ranges) in about a second, where the OEHLIN'R.dat data file was a shade under 500Mb and the programs and data are on a network drive (not local). The sort order for me was Item, Customer, Invoice date.

My ADS32.DLL is version 1.12.54.2989, which may be more current than what you have, but with current Adagio versions installed, the ADS is likely not too far behind.

I presume that your client's history is significantly larger than this, but I did not see any order of magnitude slowness when selecting a single item number for the inquiry on company data with a reasonable large history detail file.

As for your original question about 'what could have changed overnight', do they regularly do the single item/customer lookup? Just so the speed comparison is not based on the scenarios you found in your tests. Also, Miscrosoft released their round of Windows Updates yesterday, so it is entirely possible that one of these had an influence since this was a potential change yesterday. Anything else installed or changed at your client site yesterday, either Adagio related or not?

I am able to replicate the problem with their data on my computer. I will send you the data and you will be able to replicate it too. My ADS32.DLL version is 1.12.54.2983.

I tried another set of large data and interestingly, the slowness did not occur for a single item/single customer, nor for a single item/customer range, but it did occur for a item range/single customer. No matter what sort order I selected. So apparently the slowness is more fickle, I'm sorry to say.

I was aware of the Microsoft Windows Updates and I asked about that. They told me that they do not have automatic install turned on and they have not chosen to install them.

I am guessing that nothing has changed from yesterday, except they did a single item lookup today, and they had done an item range lookup yesterday. So I withdraw that part of my questions.

Steve