DevForce Community Forum : DatasourceOnly vs InvokeServerMethodAsync http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2009 : DatasourceOnly vs InvokeServerMethodAsync Sat, 11 Apr 2026 05:06:53 -700 Sat, 23 Jan 2010 14:44:19 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=1626 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ DatasourceOnly vs InvokeServerMethodAsync : Hi, Ive got listings in my app... http://www.ideablade.com/forum/forum_posts.asp?TID=1626&PID=6113#6113 Author: *Calsy
Subject: 1626
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
]]> Sat, 23 Jan 2010 14:44:19 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=1626&PID=6113#6113