Intersoft Community - WebGrid Enterprise - DataCacheStorage=Fileserver and query string

DataCacheStorage=Fileserver and query string

handy@intersoftpt.com — Tue, 02 Mar 2010 23:57:47 GMT

Hi Melbin,

Please look into my simple sample. I looped the records and add them into datatable. When WebGrid has 3500000 records, the cache should be at least 125Mb. Sometimes, I also got ''System.OutOfMemoryException' which failed to create the storage cache. After investigated and searched at google, here is what our developer teams found.

The reason why the cache is not created previously is because it throws OutOfMemoryException (so their server doesn’t have enough memory to hold ~64 MB data, which is required to save the object to file)

Also, we found that, implement the code below, will improve the memory smaller and faster.

dt.RemotingFormat = SerializationFormat.Binary;

If your data is still larger than your memory, it will fail when saving the file. It’s natural by .NET.

From what we googled, the only way they said is “move your server to 64 bit and put tons of memory for it”. (Server x64)

Please let me know if you have a question regarding our explanation.

Regards,
Handy

DataCacheStorage=Fileserver and query string

handy@intersoftpt.com — Tue, 02 Mar 2010 05:08:54 GMT

Hi Arun,

Yes. Our developer teams are investigating this issue now. I will let you know when I got a news for you.

Regards,
Handy

DataCacheStorage=Fileserver and query string

aiyer — Mon, 01 Mar 2010 10:17:04 GMT

Hi Handy,

Did you guys get a chance to have a look at this.

I am getting huge amount of pressure here, just give usa work around till you guys get some fix

Thanks

Arun

DataCacheStorage=Fileserver and query string

aiyer — Fri, 26 Feb 2010 05:51:48 GMT

Hi,

It's not number of rows.its when the actual data is large.we tried 35k rows.i can clearly see the cache file not getting created.it creats when the data is less.

We can't use custom paging and custom virtual load now because we have many page which need a change to implement this.

Can u try to replicate with large data? i can't sent you a sample application because the issue is happening in actual live client data.

Any quick solution will be much appreciated.

Thanks

Melbin

DataCacheStorage=Fileserver and query string

handy@intersoftpt.com — Thu, 25 Feb 2010 03:25:19 GMT

Hi Melbin,

Ok, thank you for your report. Regarding your issue, I need to gather more informations from you. May I know how many records do you have? Also, since you have a huge amount of records, have you ever tried custom paging and custom virtual load?

Regards,
Handy

DataCacheStorage=Fileserver and query string

aiyer — Tue, 23 Feb 2010 14:29:36 GMT

Hi Handy,

Thanks for the update.

We have limited the query string length.But we have found a new issue happening now.

The issue is when data exceeds an amount(it’s not row count), cache files(cache file size more than 67 MB) are not getting created on the location configured in CacheServerConnection property.We use

DataCacheStorage="fileserver" for loading grid. Since the cache files are not created, ‘load more’ and export fails.

="fileserver" for loading grid.

DataCacheStorage="fileserver" for loading grid. Since the cache files are not created, ‘load more’ and export fails.

Any solution for for why the cache files are not getting created when data size is huge?.Many of our clients are facing this issue.Please respond as quick as possible.

Thanks

Melbin

DataCacheStorage=Fileserver and query string

handy@intersoftpt.com — Fri, 05 Feb 2010 02:15:02 GMT

Hi Melbin,

File server can only accept length max 255 chars and our file name is based on the url.
If the url/query string is long , then the file server cache that we created may fail. So, could you please let me know what is the maximum size of your query string?

Regards,
Handy

DataCacheStorage=Fileserver and query string

aiyer — Tue, 02 Feb 2010 14:28:20 GMT

Hi,

We have a new major issue happening in Grid.Our grid uses DataCacheStorage="FileServer" and we have set the CacheServerConnection to a location.The pages on which the grid is placed are having query strings which are encoded.The grid was creating .bin and .cache file in the cacheserver location (aspxfilename+encodedstring.bin and aspxfilename+encodedstring.cache) before.

For some cases the length of the encoded query string is more.In this case the grid is not creating the .bin and .cache in the location,because of this filter,export,load more functionality fails.do you have any idea why this is happening when encoded query string's length exceeds certain amount?

This is a major issue for many of our clients and many of the page uses lengthy encoded query string.

Any solution will be much appreciated.

Thanks

Melbin