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!
|
| |
|
Re: Performance of V7.2 Web Components
Posted: 04 Sep 07 2:17 AM
|
| The initial load time (when a first user logs in) is pretty slow - but the caching is really good so after that the system is very quick - Id say the detail views load in about the same time as legacy web - the list views perhaps a little quicker. |
|
|
|
Re: Performance of V7.2 Web Components
Posted: 04 Sep 07 5:12 PM
|
Originally posted by Frank Chaffin
What is the performance of the V7.2 WebClient vs. the V6.x-to-V7.01 Webclient?
|
|
According to the data I've seen:
As Fast if not faster than the "old web". In some cases even faster than the Windows client.
--
rjl
|
|
|
|
Re: Performance of V7.2 Web Components
Posted: 04 Sep 07 5:14 PM
|
Originally posted by Nick
The initial load time (when a first user logs in) is pretty slow - but the caching is really good so after that the system is very quick - Id say the detail views load in about the same time as legacy web - the list views perhaps a little quicker. |
|
Did you "pre-compile" your web site(s)?
I did.. don't have the delays.
Credit to Ryan for this..:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -p C:\Inetpub\wwwroot\Gobi\SlxClient -v /Gobi/SlxClient
Of course fix the path so that it fits your deployment
--
rjl |
|
|
|
Re: Performance of V7.2 Web Components
Posted: 04 Sep 07 7:22 PM
|
Originally posted by Bob (RJ)Ledger
According to the data I've seen:
As Fast if not faster than the "old web". In some cases even faster than the Windows client.
--
rjl
|
|
RJ, is this first hand experience at your client's site or what you hear through the grape vine?
|
|
|
|
Re: Performance of V7.2 Web Components
Posted: 05 Sep 07 2:14 AM
|
No havent precompiled - I thought (hoped) the build / deploy process of app architect would do that (it should!!).
Thanks RJL
Nick |
|
|
|
Re: Performance of V7.2 Web Components
Posted: 05 Sep 07 6:22 AM
|
Originally posted by Bob (RJ)Ledger
Did you "pre-compile" your web site(s)?
I did.. don't have the delays.
Credit to Ryan for this..:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -p C:\Inetpub\wwwroot\Gobi\SlxClient -v /Gobi/SlxClient
Of course fix the path so that it fits your deployment
--
rjl |
|
RJ,
I thought when you Deployed the site in the Application Architect it compiled the site (ie created the DLLs in the SlxClient folder). What additional components are pre-compiled by the above command? |
|
|
|
Re: Performance of V7.2 Web Components
Posted: 05 Sep 07 6:39 AM
|
Yes the dlls are compiled but remember the "rest" is not until someone accesses the page. - "Just in Time compile".......
SP1 is supposed to have a "pre-compile" feature added to it.
--
rjl |
|
|
|
Re: Performance of V7.2 Web Components
Posted: 05 Sep 07 9:25 AM
|
Originally posted by Frank Chaffin
What is the performance of the V7.2 WebClient vs. the V6.x-to-V7.01 Webclient? |
|
I never really used the old web client that much. Mainly because it was too difficult (time consuming) to customize. I would only use it when I needed to customize it for a client.
That said, my experience with the performance of the new web client is equal to, or better, than the old web client. And for large amounts of data it performs *FAR* better than the LAN client. My own internal database has a couple million records. It is slow and sluggish in the LAN client, but in the new web platform, things fly by and it is finally nice to work in my own database again. |
|
|
| |
|
Re: Performance of V7.2 Web Components
Posted: 05 Sep 07 9:42 AM
|
Originally posted by Frank Chaffin
I thought when you Deployed the site in the Application Architect it compiled the site (ie created the DLLs in the SlxClient folder). What additional components are pre-compiled by the above command? |
|
Frank, this is the nature of *any* ASP.NET site. An ASP.NET page will compile to IL when it is accessed for the first time. From then on, the cashed compiled version is loaded from then on. There are DLLs that are already compiled, that's different. What gets compiled are any pages (aspx, ascx, master) that have inline code (which is all of them in the SLX web client), pages with code-behind, and anything in the App_Code directory.
If you look in the SLX web root directory, you'll see aspx, ascx, & master files that all have C# code in them. You'll also see cs files with C# code in them. IIS, the .NET framework, and your browser don't know what to do with those. The first time the site is accessed it takes all those and compiles them to DLLs and puts them in places like "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\d838b69d\f994c4a4" (directory names will vary after the Temporary ASP.NET Files folder). Then, those compiled DLLs can then run inside the CLR and use the framework. This is what gets loaded by the ASP.NET runtime and served out through IIS.
Does that make sense?
As was mentioned, SP1 will include an option that will precompile the site before copying it out to the IIS server. You can also accomplish this now with the command line tool aspnet_compiler.exe.
-Ryan |
|
|
| |
|
Re: Performance of V7.2 Web Components
Posted: 02 Oct 07 8:39 AM
|
| We have about 300 employees that currently have access to the support client. We are running 6.2.3 (soon to be 6.2.6). I am researching upgrading to v7 sp1. When we first implemented Support we had a large number of performance issues, to the point where SLX had to build customized executable files for us. We have since upgraded (to our current version) in which those customizations were included. As our company grows (we anticipate another 50 employees next year), we were hoping by moving to the web client we would no longer have the performance issues. We currently have over 750,000 tickets and nearly one and a half million ticketactivity records, plus nearly 15000 accounts, and nearly 80000 contacts. Our biggest concern is going to be performance. We average around 4000 tickets a month. Has anybody heard or know of customers with a large number of users and a large database having performance issues with this version. I know this is a rather new version so I am sure the number of large customers is rather small. But if anybody could shed some light on this for me it would be greatly appreciated. |
|
|
| |
|