The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
SLX performance
Posted: 13 Oct 09 4:43 PM
|
When i switch over to the Notes-Histopry Tab in slx , for this orgs with many Notes , it is very slow. THis is the query getting executed. I looked at the exec plan in sql and everything seems to be in order with only one Table scan against picklist table(which i created an index)
on sql server its gets executed in 0.1 secs and it is taking ~15 secs to show up in slx client. Our App server sits across a WAN and that is what i thought the reason woudl be. Recently i created a Remote office and checked that in that RO server and the same thing(maybe ~12 secs now). Why is this huge delay. There were no clusteered indexes in the table and i created one with the ID.
Anyone have any ideas?
SELECT A1.HISTORYID, A1.ATTACHMENT, A2.TEXT A2_TEXT, A1.COMPLETEDDATE, A1.USERID, A1.CONTACTNAME, A1.RESULT, A1.DESCRIPTION, A3.LONGCATEGORY A3_LONGCATEGORY,A3.HISTORYID,A2.ITEMID FROM HISTORY A1 INNER JOIN PICKLIST A2 ON (A1.TYPE=A2.ID) LEFT OUTER JOIN AAM_HISTORY_EXT A3 ON (A1.HISTORYID=A3.HISTORYID) WHERE ((A1.TYPE<>262162) OR (A1.USERID='U6UJ9A00004D')) AND (A1.ACCOUNTID = 'A6UJ9A0013KQ') AND (A1.TYPE <> 262156) Order By A1.COMPLETEDDATE Desc
|
|
|
|
Re: SLX performance
Posted: 13 Oct 09 5:41 PM
|
Have you looked into the query using the the SLX Profiler?
The SLX Profiler will give you several additional details: - Parse time - Prepare time - Secure Time - Execute Time - Get Rows Time - Log time
The query may indeed get executing on under a second on the SQL server, but how long does it take for the data to reach the client? (Network Latency)? By using the SLX Profiler, you will get the stats for the execution as they are gather on the client side, it may help you identify where your bottleneck lies. |
|
|
| |
|
Re: SLX performance
Posted: 14 Oct 09 8:29 AM
|
thanks raul! Did not check that . i was looking at the profiler to only get the sql running. Will look into it more closely to get the other timings.
thanks Mike! will check out that doc
|
|
|
|
Re: SLX performance
Posted: 14 Oct 09 2:18 PM
|
Mike , Did both the things and Grid is now much much faster............till the user sorts on one column and from that point onwards slow again.
In your screenshots i saw that the column completed date is sorted Desc on Design time. I tried that and still it is slow from that point. Finally to get the rows sorted by Completeddate, i had to enforce an "order by" in the Grid sql in CommonCheckBoxChange(Sender) function in script System:Notes History Common(and hope noone ever dbclick the header to sort)
Next Question: How can i speed up the Columnheader Sort event in a slx grid?
I have all sorts of performance issue with slx in our shop as the app/db server is sitting across a WAN. They are bring in WAN acceleration software from Riverbed systems to boost performance on WAN. Dont know if that is going to help
Thanks! |
|
|
|
Re: SLX performance
Posted: 14 Oct 09 2:27 PM
|
Switch off the "Sortable" property. You will find it much faster as whole grid isn't loaded into memory. |
|
|
|
Re: SLX performance
Posted: 14 Oct 09 4:33 PM
|
That creates a problem where grid.Getcurrentfield returns NULL when No rows returned after Notes filters. Didnt want to complicate further;so left it like that. Now the overall perfmance is much better.
Still the column header DBClick is running slow. It is quite a bit of a learning curve for me;otherwise we should go with slxweb
|
|
|
|
Re: SLX performance
Posted: 22 Oct 09 1:53 PM
|
Now everything is in order except for 3 users which includes my ID too Any idea why the loading should be slow for some and not for all. I debugged and it is showing the time lag at CommonCheckBox Change Sub in the Notes-History common script. grdHistory.Active = True
Any ideas? I have already cleared the cache and user options
When you login as other in that machine , it is faster. When you login and that user in another machine it is slow. So it is consistent for these userids
I have already cleared the cache and user options and reboot of server and slx/XP client.
|
|
|
|
Re: SLX performance
Posted: 22 Oct 09 2:23 PM
|
I would suggest you once again plug in the SLX Profiler on that machine. Get results with one user and then results with the other. Also, extract the actual queries and compare the resultsets.
|
|
|
|
Re: SLX performance
Posted: 22 Oct 09 5:08 PM
|
Thanks Raul! But i have tried that out already. The Getrows(ms) is way more for these 3 guys who are having a performance issue. I debugged and it is coming to that line where the Grid is made active and that is where it takes time . What next?
Called slx support and they made me overlay a blank DBs plugins table and that is fast.(But there are no groups except the OOTB) So this must be something with groups for these guys. |
|
|
|
Re: SLX performance
Posted: 22 Oct 09 6:15 PM
|
You mentioned that the GetRows takes longer for the affected users, have you looked at how much data they have?
How does their record count differs from other users? Also, how about their Blob sizes?
Modify their queries to figure out how much data they are retreiving out of hte Notes fields:
SELECT SUM(LONGNOTES) FROM HISTORY ..... (ADD YOUR CONDITIONS, ETC).
I don't see how the Plugin table would affect a user's load of a Grid, but then again, SAGE knows better.
GetRows is the time that it takes for the client to receive the actual data, thus my inclination to review the volume of data that they are receiving. |
|
|
|
Re: SLX performance
Posted: 23 Oct 09 9:12 AM
|
Ya, But i always compare apples to apples when it comes to performance testing and have been very successful in the past in various platforms.
Here... it is the same exact Org and the same conditions. Only thing which differs is the userid of the logged on user. and in debug, if i switch over to a user who do not have these issues the grid refreshes way fast. So this has to be something to do with the data handlers for a slx user. |
|
|
|
Re: SLX performance
Posted: 23 Oct 09 9:47 AM
|
Nevermind. I got it.
Rebuild all indexes in History table and it is fine now. Thanks! |
|
|
|