The main benefit of SET SMARTQUERY ON is that it will cache query results persistently (even across reboots) and only throw the smartquery cache away if any of the tables involved in a query has been modified since the query was cached. For huge tables with complex joins this results in massive performance gains.
You typically use SMARTQUERY on WORM tables i.e. Write Once Read Many. If you think about it, why even bother to perform query optimization if you already have a resultset and the tables in the query have not been modified in any way for the exact same query. This is the basis of intelligent queries and that’s what SMARTQUERY technology provides for you.
In this latest beta, I am now seeing SQL selects on tables containing 5,000,000 rows in <1ms.
Some of my WebApps run ok in WebPreview but very slowly (or not) with the Browser (Firefox, localhost).
Are there hardware specifications for the Cloudserver? (f.e. processor(s), speed, memory).
I have to find out what’s wrong with my little (UTF8) app.
I don’t think UTF-8 has any effect on the performance. I use it exclusively for all the web apps i write.
You must be doing something that is causing multiple refreshes to a page.
If you install “fiddler” (just google it) you can use that to watch requests and results sent back from the server.
I would recommend using Google Chrome or IE. I’m not a firefox fan.
Is there any performance advantage in case i import this table to my Lianja DB or the sql execution/performance will be same?
yes the native format is faster particularly when multiuser and the SQL query optimizer will perform better if you have indexes in columns that you are querying on.
If that’s a 1Gbs LAN then your file copy is only 88Mbs which is pretty slow.
There could be many reasons for this so before you look at your application you need to sort this out first.
Make sure that you do not have conflicting ip addresses on the LAN .
Google “windows test lan speed” and make sure the connections are ok.
Rule #1 check the Ethernet cables and replace them to make sure
Rule #2 check your Ethernet switch
Rule #3 run performance monitor on the server to see if something is eating cpu, disk or network
Rule #4 make sure virus checkers aren’t killing performance by temporarily disabling them