[webkit-dev] JavaScriptCore Garbage Collector Invocation

2012-02-06 Thread Harendra chawla
Hi, I have been trying to optimize or somehow control the invocation of the Java Script Core's Garbage Collector by changing certain values like the highWaterMark and minBytesPerCycle of Heap.cpp. By default the value of minBytesPerCycle is 512 KB, but when i change it to 2 MB i found some

Re: [webkit-dev] JavaScriptCore Garbage Collector Invocation

2012-02-06 Thread Ashod Nakashian
Hi, For x86 the gain is about 300 msĀ  For ARM(embedded) core getting around 150 ms. I have interest in profiling JSCore. Would you share your testbed/benchmark and methodology for the benefit of the community? It'd be useful for everyone to review/reproduce your results as well as improve

Re: [webkit-dev] JavaScriptCore Garbage Collector Invocation

2012-02-06 Thread Geoffrey Garen
Hi Harendra. Is there any side affect with the changes i have made with minBytesPerCycle from 512KB to 2 MB? More memory use. Is there any other i can optimize the performance or control the invocation of GC? That is the subject of decades of computer science research. Geoff

Re: [webkit-dev] JavaScriptCore Garbage Collector Invocation

2012-02-06 Thread Filip Pizlo
Hi, I have been trying to optimize or somehow control the invocation of the Java Script Core's Garbage Collector by changing certain values like the highWaterMark and minBytesPerCycle of Heap.cpp. By default the value of minBytesPerCycle is 512 KB, but when i change it to 2 MB i found

[webkit-dev] wincairo winlauncher still requires Safari?

2012-02-06 Thread Tim Stowell
Hi, I've built the wincairo port of webkit, but both in debug and release mode trying to execute winlauncher shows a pop-up message saying failed to determine path to safari directory Is it normal that Safari is required even to use the winlauncher? Is there any way I can use wincairo-webkit in

[webkit-dev] What is the license policy of a reviewing patch on Bugzilla (not yet landed to main trunk)?

2012-02-06 Thread Gyuyoung Kim
Hello WebKit folks, I am wondering what is the license policy for reviewing patches on bugzilla (not yet merged to main trunk). As you know, contributor should agree legal terms related to license(LGPLv.2.1, BSD) before submitting to bugzilla. So do the legal terms apply to final patches that

Re: [webkit-dev] What is the license policy of a reviewing patch on Bugzilla (not yet landed to main trunk)?

2012-02-06 Thread Adam Barth
IANAL, but here's what the bugs.webkit.org attachment page says: == WebKit Contribution Terms: Hello and thank you for contributing a patch. Here is our licensing policy and terms for contributing code to the WebKit project. If you are sending in a patch to existing WebKit code, you agree

Re: [webkit-dev] What is the license policy of a reviewing patch on Bugzilla (not yet landed to main trunk)?

2012-02-06 Thread Gyuyoung Kim
Adam, Thank you for your reply. -- Gyuyoung. --- Original Message --- Sender : Adam Barthaba...@webkit.org Date : 2012-02-07 10:20 (GMT+09:00) Title : Re: [webkit-dev] What is the license policy of a reviewing patch on Bugzilla (not yet landed to main trunk)? IANAL, but here's what

Re: [webkit-dev] What is the license policy of a reviewing patch on Bugzilla (not yet landed to main trunk)?

2012-02-06 Thread Ryosuke Niwa
In principle that should be the case. But I've seen cases where people didn't realize some files they uploaded on Bugzilla weren't compatible with LGPL or BSD until the review process so we should probably judge on case-by-case basis in practice if the patch contains new files or code imported