A horrible discovery

My blog has moved.
You can view this post at the following address:
http://www.osherove.com/blog/2003/11/4/a-horrible-discovery.html
Published Tuesday, November 04, 2003 11:27 PM by RoyOsherove
Filed under:

Comments

Tuesday, November 04, 2003 6:37 PM by Chris Stewart

# re: A horrible discovery

100 MB!?!?!
Tuesday, November 04, 2003 6:42 PM by Rob Chartier

# re: A horrible discovery

SharpReader has always been a memory hog, but its to be expected with what its doing. And it grows the longer you use it. Hell it takes a few minutes just to load.

Take a look at some of the other processes in memory, like Explorer.exe. What is it sitting at? I choose to use an alternate shell (geoshell) with alot less overhead (currently under 6mb).
Tuesday, November 04, 2003 7:04 PM by Joe Kaplan

# re: A horrible discovery

One nice thing about RSS Bandit (which also uses lots of memory) is that when you minimize it to the tray, it drops it's working set to the minimum (about 2MB on my machine) but keeps working in the background regardless. When in maximizes again, it only reallocates the memory it needs, so it starts over much smaller.
Tuesday, November 04, 2003 7:07 PM by Roy Osherove

# re: A horrible discovery

joe - that's pretty cool!
and chris - yeah 1-0-0 MB.
Tuesday, November 04, 2003 7:57 PM by James Avery

# re: A horrible discovery

Feeddemon is only about 20MB open, and shrinks to 2MB when in the taskbar. This is the main reason that I switched.

-James
Tuesday, November 04, 2003 9:15 PM by Blair Stephenson

# re: A horrible discovery

Yep, mine was sitting at around 125mb.

I've just sorted out the number of items held and it's down to 83mb.
Tuesday, November 04, 2003 9:26 PM by Steve

# re: A horrible discovery

Here's some info about SharpReader that I discovered using the CLR Profiler:
http://www.furrygoat.com/archives/000563.html#000563

Basically, 58MB of just string allocations, etc.
Tuesday, November 04, 2003 9:42 PM by Nino Benvenuti

# re: A horrible discovery

Yep. That's why I started looking for another RSS reader.. James convinced me to switch to FeedDemon. I really like it..except for one or two minor things. I'm going to re-evaluate RSS Bandit, but FeedDemon is working pretty well for me.

-Nino
Tuesday, November 04, 2003 10:13 PM by Dylan Greene

# re: A horrible discovery

100 megs isn't much... for a Java app. Is this a .NET client issue or a SharpReader issue? I'm using NewsGator, but I don't know how much memory it uses since windows only reports Outlook 2003's memory usage (62 megs currently, with about 100 feeds).
Wednesday, November 05, 2003 1:30 AM by Brian Desmond

# re: A horrible discovery

I generally clear out my saved posts every 15 or 30 days and that will help clear up the memory usage in Sharpreader. I only have about 40 feeds subscribed, but I don't delete posts (have about 5100 right now). Deleting them brings the memory usage down.

I think it has something to do with Sharpreader loading its databases into memory rather than reading them from disk as necessary (just speculating).
Wednesday, November 05, 2003 1:35 AM by AsbjornM

# re: A horrible discovery

Mine uses 400-600MB, well, I have some feeds, and about 74000 posts :) (won't delete).
But it looks like Sharpreader keeps everything in memory, It is very tempting to write an aggregator that uses sql server or something..
Monday, November 10, 2003 9:37 AM by Tony B

# re: A horrible discovery

Mine takes 32MB (100 feeds, 10000 posts), but drops down to 1MB or less when minimised - No problem at all