Is Script.aculo.us extremely slow

I am developing a project for my school and I am new to Script.aculo.us.
Everything works great it’s just extremely slow. I spoke with one of my
professors and he suggested some poking around in the forums.

The only other thing I could think of was that our development server on
campus is extremely slow and once it moves over to production it will
perform much faster.

I was wondering if anyone has any experience using this and if it was
slow for them.

Thanks in advance

Chris H. wrote:

I am developing a project for my school and I am new to Script.aculo.us.
Everything works great it’s just extremely slow. I spoke with one of my
professors and he suggested some poking around in the forums.

The only other thing I could think of was that our development server on
campus is extremely slow and once it moves over to production it will
perform much faster.

I was wondering if anyone has any experience using this and if it was
slow for them.

Thanks in advance

works fast for me…

Most of Script.aculo.us are effects like fade, etc. And the editable
fields, etc do not do that much on the server. So, I don’t think it has
to do with the server or script.aculo.us.

How is it slow?

Have you tried various things, like firebug, that can profile your code?

Am 29.12.2007 um 03:49 schrieb gemblon (t.b.):

campus is extremely slow and once it moves over to production it will
perform much faster.

I was wondering if anyone has any experience using this and if it was
slow for them.

Thanks in advance

works fast for me…

here, too. In all browsers no problems at all.


jochen

Firefox and IE. Anything involving the Script.aculo.us is slow. Im
using an auto_complete field. When you begin to type after 3 characters
it should generate a list of options. In order for it to work you have
to stop typing because it will never keep up with you. I have to wait
about 4 seconds in order to see a populated list.

I am also using some of the AJAX stuff like remote_function so I do not
have to reload the page every time. This is extremely slow too. I have
made some clickable areas on the screen and when a user clicks on one I
use replace_html inside the div. This again takes about 5 seconds to
see a response.

I just wasn’t if it was always going to be this slow. I think users
will feel like its not working bc it is taking so long.

Thanks for all the comments.

Well that depends on where is slow. If is slow when loading the pages,
then probably you can reduce the js (if depend on it) but if it’s slow
after the page has been load probably it’s not a scriptaculous problem.
What browser are you using?

On Dec 30, 2007 11:08 AM, Chris H.
[email protected] wrote:

Firefox and IE. Anything involving the Script.aculo.us is slow. Im
using an auto_complete field. When you begin to type after 3 characters
it should generate a list of options. In order for it to work you have
to stop typing because it will never keep up with you. I have to wait
about 4 seconds in order to see a populated list.

This almost certainly has nothing to do with the server since it’s all
javascript code running in the browser at this point. How much RAM
does the client machine have?

I don’t know about IE, but every version of Firefox I’ve used so far
seems to have one or more memory leaks which means that Firefox slows
down over time, killing Firefox and restarting it often improves the
performance dramatically, at least for a while.

It seems to be getting better with each release of Firefox but…

I am also using some of the AJAX stuff like remote_function so I do not
have to reload the page every time. This is extremely slow too. I have
made some clickable areas on the screen and when a user clicks on one I
use replace_html inside the div. This again takes about 5 seconds to
see a response.

Some of this might be a server problem, but I’m guessing that if
you’re seeing the kind of performance you are for local javascript
execution, that it’s the same story.


Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

I’m using an AJAX request to populate a multi-record edit form, it takes
2793ms in development mode and 93ms in production mode, Rails 1.2.6.

On Dec 31, 2007 5:01 AM, Rick DeNatale [email protected] wrote:

This almost certainly has nothing to do with the server since it’s all

I am also using some of the AJAX stuff like remote_function so I do not

Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/


Ryan B.
http://www.frozenplague.net
Feel free to add me to MSN and/or GTalk as this email.

Try also using firebug - it’s great for seeing how long the browser
waited for the response etc (and for a whole host of other things)

Fred

OK, I will try them all and see what happens. Thanks a lot everyone

In my view it nothing do with the client at all. Your server is slow.
Try
switching to production mode and see if it is this slow as well. If this
doesn’t help index the columns of the database table you are using for
autocomplete thing. If even this doesn’t work try hosting the
application on
another server(faster).
In my view this is nothing to do with client side things like browser,
machine and JS libs.

On Dec 30, 2007 9:38 PM, Chris H.
[email protected]

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs