Print Page | Close Window

DatasourceOnly vs InvokeServerMethodAsync

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2009
Forum Discription: For .NET 3.5
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1626
Printed Date: 28-Apr-2025 at 5:12am


Topic: DatasourceOnly vs InvokeServerMethodAsync
Posted By: *Calsy
Subject: DatasourceOnly vs InvokeServerMethodAsync
Date Posted: 23-Jan-2010 at 2:44pm
Hi, Ive got listings in my app that require that the data is always retrieved fresh from the database so the latest data is shown. I was doing perf testing this morning and found if i do a normal executequeryasync with querystrategy of datasourceonly the data took 4.5 seconds to retrieve. Whereas if i took the same call to a InvokeServerMethodAsync method and compile the data at the server and send the cache back and retrieve the data than from that cache it cuts the time back to 2.5 seconds to retrieve (nearly half).
 
Is there any reason why i shouldnt do all my data calls that require datasourceonly via InvokeServerMethodAsync methods? It seems a little round about, but if its going to cut my data calls by half than its a winner in my books.
 
Thanks


Print Page | Close Window