Comments on: Rick Rawson on: Why I use Chandler and what would make me stop. http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/ Thu, 12 May 2011 16:41:36 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: paulo http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-322378 paulo Thu, 10 Dec 2009 14:00:32 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-322378 at the moment chandler is just using below 2 mb. python is using almost 100 mb. I do have 4 gb of ram so it is not an issue. at the moment chandler is just using below 2 mb. python is using almost 100 mb.
I do have 4 gb of ram so it is not an issue.

]]> By: David K. http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-177137 David K. Sat, 13 Jun 2009 09:02:14 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-177137 Although I have not delved into Chandler code, it seems that part of the problem is architectural in nature. E.g. Python libraries, too much virtualization, object-caching, and platform-independence. In the superconducting nanocomputers of the far-future, such elegant technologies might be fine. However, most of us with even modern hardware would benefit from a little more performance optimization. For example, there seems to be a large OSX community. How about rewriting the app using the high-quality object-oriented GUI frameworks that exist for OSX? If you want to abstract some "business logic" above this, fine, but GUI implementation is, IMHO, too platform-dependent anyway. From my personal experience, there is a lot of emphasis on generality and abstraction, but few frameworks provide the level of performance and robustness that allows this to work in "consumer" deployments. I mean, really, who wants to have their end-users see a Smalltalk stack dump? :) My 2 cents. I love this project and want to see it fly, and show off its design merits. Not bog and dump due to implementation choices... Although I have not delved into Chandler code, it seems that part of the problem is architectural in nature. E.g. Python libraries, too much virtualization, object-caching, and platform-independence.

In the superconducting nanocomputers of the far-future, such elegant technologies might be fine. However, most of us with even modern hardware would benefit from a little more performance optimization.

For example, there seems to be a large OSX community. How about rewriting the app using the high-quality object-oriented GUI frameworks that exist for OSX? If you want to abstract some “business logic” above this, fine, but GUI implementation is, IMHO, too platform-dependent anyway.

From my personal experience, there is a lot of emphasis on generality and abstraction, but few frameworks provide the level of performance and robustness that allows this to work in “consumer” deployments. I mean, really, who wants to have their end-users see a Smalltalk stack dump? :)

My 2 cents. I love this project and want to see it fly, and show off its design merits. Not bog and dump due to implementation choices…

]]> By: Mimi Yin http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-25763 Mimi Yin Tue, 15 Jul 2008 01:42:07 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-25763 Hi Nate, Yes, having a lot of data can make Chandler slower. We have been discussing a number of short-term solutions to address this problem sooner rather than later on the Chandler Development list: http://lists.osafoundation.org/pipermail/chandler-dev/2008-July/010108.html 1 has already been implemented and will be coming out in the next release: https://bugzilla.osafoundation.org/show_bug.cgi?id=12234 Other users have also reported that Chandler gets bigger if you leave it open for long periods of time (multiple days?) So quitting and restarting may help as well. Best, Mimi Hi Nate,

Yes, having a lot of data can make Chandler slower. We have been discussing a number of short-term solutions to address this problem sooner rather than later on the Chandler Development list: http://lists.osafoundation.org/pipermail/chandler-dev/2008-July/010108.html

1 has already been implemented and will be coming out in the next release: https://bugzilla.osafoundation.org/show_bug.cgi?id=12234

Other users have also reported that Chandler gets bigger if you leave it open for long periods of time (multiple days?) So quitting and restarting may help as well.

Best,
Mimi

]]> By: Nate the Great http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-25309 Nate the Great Thu, 10 Jul 2008 18:05:28 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-25309 Is anyone else seeing Chandler consume 500 MB of RAM? It's only doing a little over 100 on my machine (according to Task Manager). 500 MB would be ridiculous, but I can live with 100. Is it possible that having a large number of tasks/emails makes it bigger/slower? Is anyone else seeing Chandler consume 500 MB of RAM? It’s only doing a little over 100 on my machine (according to Task Manager). 500 MB would be ridiculous, but I can live with 100.

Is it possible that having a large number of tasks/emails makes it bigger/slower?

]]> By: Grant Baillie http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-20643 Grant Baillie Fri, 23 May 2008 18:20:16 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-20643 Alex, you're right that VM usage is a big factor, although there are cases where the CPU is doing too much, too. So far as why this is, there are many contributions. The biggest one is that architectural decisions taken early on in the project meant that way too much data is being persisted. For example, the app persists all schema and GUI layout information, leading to on-disk and mapped memory bloat. (There is also redundancy in the data stored on disk that leads to more of this kind of bloat). In any event, we are aware of these issues and are working actively on addressing them post-1.0. At the moment, Phillip Eby is doing a bunch of infrastructure work in this area: See http://lists.osafoundation.org/pipermail/chandler-dev/2008-February/009667.html for an outline of the plan. Specific and detailed technical information of his work can be found on the PEAK mailing list at: http://www.eby-sarna.com/pipermail/peak/ Alex, you’re right that VM usage is a big factor, although there are cases where the CPU is doing too much, too. So far as why this is, there are many contributions. The biggest one is that architectural decisions taken early on in the project meant that way too much data is being persisted. For example, the app persists all schema and GUI layout information, leading to on-disk and mapped memory bloat. (There is also redundancy in the data stored on disk that leads to more of this kind of bloat).

In any event, we are aware of these issues and are working actively on addressing them post-1.0. At the moment, Phillip Eby is doing a bunch of infrastructure work in this area: See

http://lists.osafoundation.org/pipermail/chandler-dev/2008-February/009667.html

for an outline of the plan. Specific and detailed technical information of his work can be found on the PEAK mailing list at:

http://www.eby-sarna.com/pipermail/peak/

]]> By: Alex Kavanagh http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-20460 Alex Kavanagh Thu, 22 May 2008 07:56:35 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-20460 I think it is simply too big. It uses 504MB of RAM, 175MB resident, on my system. I had to upgrade my laptop to 2GB RAM to make it work responsively, otherwise it was always hitting the swap to get its code back into memory. This made it almost unusable. Why is it so big? Otherwise it's great although it would be useful if the side panel notes section had formatting options. I think it is simply too big. It uses 504MB of RAM, 175MB resident, on my system. I had to upgrade my laptop to 2GB RAM to make it work responsively, otherwise it was always hitting the swap to get its code back into memory. This made it almost unusable. Why is it so big? Otherwise it’s great although it would be useful if the side panel notes section had formatting options.

]]> By: Mimi Yin http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/comment-page-1/#comment-20382 Mimi Yin Wed, 21 May 2008 17:22:12 +0000 http://blog.chandlerproject.org/2008/05/21/rick-rawson-on-why-i-use-chandler-and-what-would-make-me-stop/#comment-20382 To Rick's point, performance as an important problem we need to continuously address. The performance issues users have run into vary from platform to platform and certainly, Chandler fairs better on newer, more powerful computers and worse on older ones. What would help us the most are reports from users on exactly which user actions are slow. User actions that have been most frequently reported as slow include: - Switching collections<br> - First time launch<br> - Quitting<br> - Purging obsolete data To Rick’s point, performance as an important problem we need to continuously address. The performance issues users have run into vary from platform to platform and certainly, Chandler fairs better on newer, more powerful computers and worse on older ones. What would help us the most are reports from users on exactly which user actions are slow.

User actions that have been most frequently reported as slow include:

- Switching collections
- First time launch
- Quitting
- Purging obsolete data

]]>