Good day,
we have a number of pages in a website, that use a Radgrid with custom skinning and column templates. Our issue is that the very first grid database update operation (insert, change, delete) is very slow (in the order of 10 to 15 seconds),
while all the consecutive operations are very fast (in the order of a fraction of a second).
We experience this behavior regardless of the first page that we operate into, and regardless of the consequently opened pages, so there is no relation between the first grid of operation, and the consequent pages that are opened, and their grids,
it's always the first grid database update operation that's slow. We already verified that this is also not PC related. Very different systems behave identically.
Basically, once the application is running and has performed an update operation, the problem goes away, until the application is restarded in Visual studio, and a first database update operation is performed.
Given the spectrum of possible places to look at, to pinpoint the origin of this behavior, we would like to know if anybody has experienced something similar, or has a suggestion on the matter.
Thanks in advance.
we have a number of pages in a website, that use a Radgrid with custom skinning and column templates. Our issue is that the very first grid database update operation (insert, change, delete) is very slow (in the order of 10 to 15 seconds),
while all the consecutive operations are very fast (in the order of a fraction of a second).
We experience this behavior regardless of the first page that we operate into, and regardless of the consequently opened pages, so there is no relation between the first grid of operation, and the consequent pages that are opened, and their grids,
it's always the first grid database update operation that's slow. We already verified that this is also not PC related. Very different systems behave identically.
Basically, once the application is running and has performed an update operation, the problem goes away, until the application is restarded in Visual studio, and a first database update operation is performed.
Given the spectrum of possible places to look at, to pinpoint the origin of this behavior, we would like to know if anybody has experienced something similar, or has a suggestion on the matter.
Thanks in advance.