Speed of JavaScript Asset Map

(Douglas (@finnatic at @waikato)) #1

Waikato upgraded to a Matrix version with the JavaScript Asset Map some weeks back with Squiz NZ's help.

 

Since upgrading I've noticed that the speed of the Asset Map is a bit variable from machine to machine, and after initially suspecting it was a caching issue are now wondering if others have seen speed differences between devices.

 

Alternatively... does anyone have suggestions on how to speed up the performance of JavaScript functionality like the Asset Map?  I'm wondering if simply adding RAM to slow machines might be something we could suggest.

 

(Nic Hubbard) #2

What functions of the asset map are show? What browser and version are you using? What OS?

(Douglas (@finnatic at @waikato)) #3

Hi Nic,

 

What I've found on Chrome Canary (35) on Mac OS X 10.6.8 is that opening a folder can result in a delay as the JS does whatever it does.  That delay doesn't exist on Chrome (34) on Windows 7.  The Mac itself is a bit elderly (an older style Mac Pro) with limited (2GB) ram, which might be the issue.

 

Douglas.

(Nic Hubbard) #4

Have you tried other browsers too? I have always found javascript in Safari to be super fast.

 

Also, if I were you, I would download Charles, and see if it is the request taking a long time, or just javascript being slow.

(Douglas (@finnatic at @waikato)) #5

Hm.  Yes, switching between Chrome, Firefox and Safari, it's Chrome that's slow - Firefox and Safari are both comparable to the Asset Map performance in Chrome on Win7.

 

I'll have a look into what I can do to address that slowness in Chrome.

(Anthony Barnes) #6

You might also want to check any extensions you've got installed on Canary. Since that's the dev version of Chrome there are often issues yet to be ironed out with some extensions (e.g. I've heard Adblock cause issues a few times).