Hai

there may someone post unwanted msg.

i know about the cache , i have no idea how to implement it  , but i have
searched and

placed the code above , would you go through tat , let me know is there any
correction...


On 11/20/08, Theraot <[EMAIL PROTECTED]> wrote:
>
>
> Hello...
>
> 1) when using in SQL "SELECT * FROM...." the engine takes extra time
> to look for the fields of the table (who knows, may be they
> changed...), but if you provide the list of fields, then it only need
> to check if they are valid, and that last part can be fasted up with a
> stored proedure (<- and stored procedure is just like a cache). so
> avoid the "*".
>
> 2) Ok, the cache on the web page, is something, but ... that's not the
> only cache!, there is another thing called cache to take in account,
> are you doing a query every time you need the data? why, you don't
> store a copy in server memory to only query once every time a page is
> requested? (note: I mean also to release that copy soon)
>
> 3) yep, LinQ may do an speed up, because it adds another cache layer,
> if you can place the queries in method outside the webpage, much
> better.
>
> 4) sure, XML may help, it's an option to have a long period cache...
> even I don't think its needed.
>
> ...you don't even know what cache means...
>
> And why is Troy asking?, isn't this thread started by Venkatu? what's
> going on here? and wtf, with "hello"? did Venkatu use Troy as a cache?
>
> 5) may be you just have a huge flash in the front page >_< (joke),
> Want steps to speed up?
> - Measure the time of the procedures in the server, to look out what
> eating time, speed that up, check again, is already enought fast?
> not... then repeat.
>
> May the cache be with you
> ~theraot

Reply via email to