This week's book giveaway is in the OCPJP forum.
We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line!
See this thread for details.
The moose likes HTML, CSS and JavaScript and the fly likes AJAX performance Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Engineering » HTML, CSS and JavaScript
Bookmark "AJAX performance" Watch "AJAX performance" New topic
Author

AJAX performance

Matt Holloway
Ranch Hand

Joined: Oct 16, 2003
Posts: 53
I'm wondering if there are any client side performance issues with AJAX due to the client side scripting.

What I'm getting at here is the use of AJAX in a terminal services environment, if all of the client side scripting is taking place on a terminal server, would that not eventually bog down the terminal server?
Hemant Agarwal
Ranch Hand

Joined: Nov 21, 2005
Posts: 138
I want to know if AJAX would take more time to implement the same thing in other ways?
Liyaquat Ali
Ranch Hand

Joined: Nov 16, 2005
Posts: 156
Try this link,

http://www.coderanch.com/t/117483/HTML-JavaScript/Ajax-Technology

also browse Ajax discussions on this forum, U'll get Ur answer.


Excuse me while I kiss the sky (Jimi Hendrix)
Christian Gross
Author
Ranch Hand

Joined: Feb 20, 2006
Posts: 85
Performance issues? Ah yes...

I had to double check your question because initially in my response I ran on about this how if performance were an issue we would not be talking about Java. But then I reread your question and saw what you were really asking.

Since JavaScript is slower, and you are thinking about terminals, what happens? I would say, you should test it. In fact I am thinking, I SHOULD TEST it as its a valid question.

Here is what I do know:
1) JavaScript does not have a jitter. So that means every script is executed as if it were seen for the first time.
2) Browsers like IE tend to keep several pages stored in the background without releasing the resources. Firefox does not do this, but have not tried all combinations
3) Browsers when executing multiple HTML pages tend to be resource hogs. It gets worse if your machine has more memory because the browser seem to think it belongs to them!
4) Mozilla, and Firefox have a very nasty bug that every now and then will cause the browser to grab 100% CPU. Mozilla knows about this and they are trying to figure out what the problem is. The only way to stop it is to exit the browser.
5) If you use a browser and allow individuals to surf to other sites advertisements these days think that the CPU belongs to them. I have often seen Flash advertisements grab 25% of my CPU because the advertisment thinks it is cool to have snowflakes falling!

If you plan on deploying Ajax applications on a terminal server I would do it under very controlled circumstances! Things could get very quickly out of control, especially if you let the operators "surf".


Author of Ajax Patterns and Best Practices
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: AJAX performance