The Artima Developer Community
Articles | News | Weblogs | Books | Forums
Artima Forums | Articles | Weblogs | Java Answers | News
Sponsored Link •

Java Buzz Forum
New Eclipse3.1 Speed Performance

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Fred Grott

Posts: 4361
Nickname: shareme
Registered: Jan, 2003

Fred Grott is Lead Developer-CEO of ShareMe Technologies LLC -The Mobile Future
New Eclipse3.1 Speed Performance Posted: May 18, 2005 6:34 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Fred Grott.
Original Post: New Eclipse3.1 Speed Performance
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology. 		Latest Java Buzz Posts
Latest Java Buzz Posts by Fred Grott
Latest Posts From ShareMe Technologies LLC-The Mobile Future

Advertisement
There are some new charts comparing Eclipse3.1M7 performance to Eclipse3.0. Green is faster performance and less memory and red is slower performance and less memory.

The problem with this chart is that they grouped memory taken along with measurement of task performance completion. What is wrong with that type of chart?

Let me explain, several strategies were used in the ramp up to full Eclipse3.1 final release such as memory foot print of plugins, optimization of workspace memory foot print, and etc. On top of that from the user persepctive most tasks are obeserved in time measurments not memory measurements as we IDE user usually do nto have detialed reprots onthe memory used by different aspects of the EclipseIDE platform.

I know I am being picky but we need a bettter chart than this from the EclipseIDE user perspective in time measurements instead of plain percentages. Even better if time and memory taken were measured separately so that one could gauge exactly how successfull each speed optimization strategy was in the realm of the whole platform and each IDE user concern.

Read: New Eclipse3.1 Speed Performance

Topic: Disruption Previous Topic   Next Topic Topic: New Java Portal from Sys-con
Sponsored Links


Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use