I have seen that for some clients. Typically it happens when you network connection is slow and/or the specific database you are polling is large. The system is trying to scan a large database and load a huge amount of data into memory (seem like the loading into memory is the slowest part). What I usually try is to change the initial filters to narrow down (as opposed to loading all) the amount of transactions that must be loaded into memory. Then you change the filters to what you are actually looking for.
↧