From: Sascha H. <sa...@gm...> - 2010-09-18 12:57:53
|
2010/9/18 Panayotis Katsaloulis <pan...@pa...> > On 18 Σεπ 2010, at 3:01 μ.μ., Sascha Haeberling wrote: > > > > > Actually no. Of course just showing the help dialog is the worst > situation. But show me the numbers when compiling a whole project. > > No it's not the worst case scenario, since all files need to be extracted > all the time. It is not the best, it's just an indication that it slows down > things. Probably not with > I call it worst case, because the work XMLVM needs to do is minimal (just printing some text), but still everything needs to be launched and extracted. When XMLVM does "real" work, this boot-up time will be a big part anymore. > > > > > I don't think that extracting data from the OneJAR is a huge part in the > whole process. Believe me, I care about speed just as much as you do. Last > week I made some significant changes that speed up the compilation > significantly. I was able to save minutes. If the OneJAR only adds 2 seconds > to a cross-compilation, I would see it as rather insignificant. But of > course, if there are clever ways to make the OneJAR faster, I am always for > it,but I wouldn't abandon it. > > It still needs a lot of improvements and I have made some myself in the > past. Still, as Josua said, this is a benefit only for the xmlvm developer, > not user (the iphone developer). > > For an iPhone developer who compiles and saves a project 100s times, even a > 2 second penalty is too much. > > Now, for an actual case scenario, in order to do it it needs to make > changes to the xmlvm to perform it. > If I make these changes, I prefer to submit it as a patch, instead of > discussing here ;) > Well now you are digressing, this is not productive. We all use XMLVM everyday on tasks and we see how long things take. As I said, I did some benchmarking last week when I implemented quite a few speed improvements. Most of these task would run for many seconds anyway, so 2 seconds don't seem much. But please correct me, if I am wrong. As a concrete example: I was corss-compiling half of the OpenJDK library, which originally took about 5 minutes to do. After the improvements I've submitted it came down to 1.5 minutes. 2 seconds are not even noticeable in such a scenario. What I want to say is this: If most usual "real" tasks have a duration of many seconds, then making a change as drastic as "getting rid of OneJAR" only to save a minimal barely noticeable speed improvements seems out of proportion. // Sascha > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |