If I may ask, where is the greatest source of the performance issue? Is python compiled, or interpreted, or compiled to a VM? Are there algorithmic issues such as perhaps data retrieval in the repository?
Hank On 6/15/06, Katie Capps Parlante <[EMAIL PROTECTED]> wrote:
hank williams wrote: > I'm sorry. I am not angry at all and I hope not to be rude. Just > strident. If I have crossed than line I apologize profusely. I have > no stake in this - I've never lost any data or anything, and as I have > said several times I really would love to see this succeed. I have > spent a fair amount of my life thinking about PIMs and this is an > enormous effort in trying to make a leap. No worries, I appreciate your desire to see the project succeed. > That said, it was amazing to me to read in the archives someone > defending performance. Sometimes when you are in the trenches you end > up doing group think, and it is useful to have some outside.. er > "perspective". Sometimes hearing the truth from someone who can speak > truth without consequences is helpul - though it may not always > initially appear to be so. Yup, some comments on the list may have indicated that we're not taking performance seriously. In reality we think of it as one of our top risks. > I may be more thick skinned than most but it is always helpful to me > to hear peoples totally unvarnished thoughts. But my intent is not to > offend. If I had just said "oh it seems a little slow" it probably > would not have gotten the point across. > It is important to us to keep the lists civil (often not the standard for net culture), so just some friendly push back on the tone. >> > Recently, I purchased a new Intel MacBook, and so i thought it was >> > time to try again. >> >> If you're trying the 0.6 release, the 0.7alpha2 release, or any prior >> build you are not running a native Intel Mac app. To get the native >> build, you can wait for 0.7alpha3 or build from source. >> > > Thats good news. Though I still suspect there is a problem, because > other power pc apps feel ok. Certainly there are a number of problems, some fixed in the next release and some remaining. It will continue to be a focus. >> We understand that Chandler performance on those releases is a big >> problem, and have been working on improving it. In addition to having a >> native build for Intel Mac, 0.7alpha3 should have many performance >> improvments. We'll still have work to do on performance, but it should >> be less painful for those of us who are using it day to day (Mitch and >> several other folks on the team are currently dogfooding Chandler). >> >> > I am concerned that years after this >> > effort began that you "cant get there from here". >> >> Fortunately, I am more confident than you :) which is good because I'm >> responsible for making it happen (along with the rest of the core team >> working on Chandler). We appreciate the patience of everyone who has >> followed us through this sometimes epic journey. >> > > Thats great. I do wish you luck. I know the team is full of smart > people and my only real window into the process has been observing the > bits. Thanks for the well wishes. I'm looking forward to having more usable bits for you and others to play with. Cheers, Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
