tag:blogger.com,1999:blog-20975090.post1242725305769612699..comments2026-02-05T05:43:08.642-06:00Charles Oliver Nutterhttp://www.blogger.com/profile/06400331959739924670noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-20975090.post-23304659900558235712007-09-13T04:42:00.000-05:002007-09-13T04:42:00.000-05:00Vladimir: No specific test that would be good for profiling, but running Rails would be a great real-world test. And yes, run JRuby from trunk; it's quite stable and easy to build.Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-46782805428470086362007-09-12T11:20:00.000-05:002007-09-12T11:20:00.000-05:00I'd focus on Rails performance. Probably the most important benchmark at all. It would be great if JRuby 1.1 comes close to MRI performance in this regard.<BR/><BR/>Something I noticed when looking at Rails performance with a profiler: <BR/>RubyModlue.includeModule() -> getRuntime().getCacheMap().clear() consumed about 10% of the complete request (including Jetty/Goldspike)<BR/><BR/>This was a very simple page though and the profiling was nothing scientific but a quickshot only (the stacktraces are impressive by the way)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-72445232469557937672007-09-12T09:27:00.000-05:002007-09-12T09:27:00.000-05:00Hi Charles,<BR/><BR/> static compiler : this will enable better unit testing integration with existing java projects. Cool.<BR/><BR/>Thank you guys for all the hard work.<BR/><BR/>BR,<BR/>~AAnjanhttps://www.blogger.com/profile/01902768305914200908noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-69808599558689973822007-09-12T07:05:00.000-05:002007-09-12T07:05:00.000-05:00Charles: Wow, profilers and memory leaks are the third soft spot for me (besides Java and Ruby), so all-in-all, very interesting suggestion!<BR/><BR/>Do you have any specific tests/test-cases to try out first? Any particular area that requires more attention?<BR/><BR/>I definitely could start with my own, home-grown scripts, but maybe there is something out there (some open performance benchmarks or tests) that are already used by you and the community?<BR/><BR/>P.S. As for the JRuby version, I'm just using JRuby hand-compiled from the trunk, right?Vladimir Sizikovhttps://www.blogger.com/profile/11263393823709082814noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-22048974283312560652007-09-12T04:30:00.000-05:002007-09-12T04:30:00.000-05:00Vladimir: For someone in your position, there's probably a perfect option: help us profile memory and performance and test multi-threaded operation. We have been working hard to improve perf and memory usage, and to make multi-threaded applications more stable, but there's only limited resources available to test and profile. Help from the community is needed...if people can identify areas where performance, memory, or threading need work, we can take it from there.Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-43517045227842496442007-09-12T03:54:00.000-05:002007-09-12T03:54:00.000-05:00Great!<BR/><BR/>Charles, is there anything that somebody like me (with java and ruby experience, but without much knowlegde on JRuby internals) could help out. I have some spare time and would like to spend it better than just watching TV. :)<BR/><BR/>Any pointers or links would be appreciated!Vladimir Sizikovhttps://www.blogger.com/profile/11263393823709082814noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-22283702194312855192007-09-12T03:25:00.000-05:002007-09-12T03:25:00.000-05:00Nice :)<BR/>Having a static compiler is a great feature !Anonymousnoreply@blogger.com