Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
What 's next?
36 views
Skip to first unread message
riadh chtara
Oct 31, 2012, 3:47:49 PM10/31/12
to
Hi guys!
After many tests, I think that we should implement the compiled js cache.
For most of script, this will reduce compiling time.
I still need that someone of you try this patch, check if the timer are in good position and give me feed back.
https://docs.google.com/file/d/0B9VtjieUwlMDR0lXWHViTkhPWXc/edit
(For more information about patch configuration check my last topic
https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.tech.js-engine/hxeOP6qJE7U)
After that I think we need to start talking about more serious staff: how to implement this: I saw the the cache implementation in necko. I like the idea of having cache in many devices(memory, hard drive). We maybe should also try compressing generated data, I tried that and it reduces 70% of file size. But I don't know how much decompression will take .
Best
Riadh
After many tests, I think that we should implement the compiled js cache.
For most of script, this will reduce compiling time.
I still need that someone of you try this patch, check if the timer are in good position and give me feed back.
https://docs.google.com/file/d/0B9VtjieUwlMDR0lXWHViTkhPWXc/edit
(For more information about patch configuration check my last topic
https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.tech.js-engine/hxeOP6qJE7U)
After that I think we need to start talking about more serious staff: how to implement this: I saw the the cache implementation in necko. I like the idea of having cache in many devices(memory, hard drive). We maybe should also try compressing generated data, I tried that and it reduces 70% of file size. But I don't know how much decompression will take .
Best
Riadh
0 new messages