Community Discussions and Support
Pegasus Mail 4.63 Build 325 Extremely Slow Closing

I think this is quite a serious problem. Other email clients, like Thunderbird,  load much faster. I've always much preferred Pegasus, but it will be a pity if the slow loading problem can't be sorted.

I think this is quite a serious problem. Other email clients, like Thunderbird,  load much faster. I've always much preferred Pegasus, but it will be a pity if the slow loading problem can't be sorted.

I have recently upgraded to 4.63 and am noticing a marked deterioration in performance upon closing/exiting the program.

I should probably be given automatic membership in the 'Gold Hoarders' society; as I have some 10GB of Pmail data collected since mid 90's,
9000 New Mails, some couple hundred folders, & 55000 messages in the main folder.  I also have an estimated several hundred
mail filtering rules applied upon closing.  

Running Windows XP Pro 2.8GHz 4GB main memory & 2 TB Pmail data drive; 50% used.

With these parameters I understand I should not expect the speed of light;
however the speed difference between this version upon closing & the previous version I used (2 Versions ago ?) is marked.

Any thoughts ??

<p>I have recently upgraded to 4.63 and am noticing a marked deterioration in performance upon closing/exiting the program.</p><p>I should probably be given automatic membership in the 'Gold Hoarders' society; as I have some 10GB of Pmail data collected since mid 90's, 9000 New Mails, some couple hundred folders, & 55000 messages in the main folder.  I also have an estimated several hundred mail filtering rules applied upon closing.  </p><p>Running Windows XP Pro 2.8GHz 4GB main memory & 2 TB Pmail data drive; 50% used. </p><p>With these parameters I understand I should not expect the speed of light; however the speed difference between this version upon closing & the previous version I used (2 Versions ago ?) is marked.</p><p>Any thoughts ?? </p>

Re the Posted Speed Fix:
Go to Tools => Options => Advanced settings and set Load Windows Internet Services ... to Always, then restart Pegasus Mail.

This was done some time ago & is still in place.

The speed on loading is also abysmal.

I think there is a problem here !

<p>Re the Posted Speed Fix: Go to <em>Tools => Options => Advanced settings</em> and set <em>Load Windows Internet Services ...</em> to <em>Always</em>, then restart Pegasus Mail.</p><p>This was done some time ago & is still in place.</p><p>The speed on loading is also abysmal.</p><p>I think there is a problem here ! </p>

No Antivirus Running/Scanning.  I'm careful about threats & only run when needed.

No Antivirus Running/Scanning.  I'm careful about threats & only run when needed.

[quote user="ArtM"]No Antivirus Running/Scanning.  I'm careful about threats & only run when needed.[/quote]

I'm not sure about this, but the reason might be that both 4.62 and 4.63 are so-called "debug builds" allowing us to do better debugging. The reason for releasing them was that there seems to be a crash condition on close which only occurs with non-debug builds. Since the speed issue didn't seem to annoy lots of people we didn't enforce figuring out what causes this apparently "non-debuggable" crash ...

<p>[quote user="ArtM"]No Antivirus Running/Scanning.  I'm careful about threats & only run when needed.[/quote]</p><p>I'm not sure about this, but the reason <em>might</em> be that both 4.62 and 4.63 are so-called "debug builds" allowing us to do better debugging. The reason for releasing them was that there seems to be a crash condition on close which only occurs with non-debug builds. Since the speed issue didn't seem to annoy lots of people we didn't enforce figuring out what causes this apparently "non-debuggable" crash ...</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

[quote user="idw"]Since the speed issue didn't seem to annoy lots of people we didn't enforce figuring out what causes this apparently "non-debuggable" crash ...[/quote]

May that be the reason for slowed down filteringspeed (SPAMhalter and self created filters) in factor three on new mails? We used PM451 before and the admins tested PM461 for a while. Because we thought, the differences are not that big we decided to have a rollout with PM463. Last Friday my colleague had a test on his real mailbox with about 200 mails in inbox ... and screemed about slowed filtering.

If there is a version available with debugoptions turned off, we may test if debug is the reason for slowing down ...

bye   Olaf

 

<p>[quote user="idw"]Since the speed issue didn't seem to annoy lots of people we didn't enforce figuring out what causes this apparently "non-debuggable" crash ...[/quote]</p><p>May that be the reason for slowed down filteringspeed (SPAMhalter and self created filters) in factor three on new mails? We used PM451 before and the admins tested PM461 for a while. Because we thought, the differences are not that big we decided to have a rollout with PM463. Last Friday my colleague had a test on his real mailbox with about 200 mails in inbox ... and screemed about slowed filtering.</p><p>If there is a version available with debugoptions turned off, we may test if debug is the reason for slowing down ... </p><p>bye   Olaf</p><p> </p>

[quote user="FJR"]May that be the reason for slowed down filteringspeed (SPAMhalter and self created filters) in factor three on new mails? We used PM451 before and the admins tested PM461 for a while. Because we thought, the differences are not that big we decided to have a rollout with PM463. Last Friday my colleague had a test on his real mailbox with about 200 mails in inbox ... and screemed about slowed filtering.[/quote]

I don't know, after all it's only a guess, and if it only affects a single user there may very well be something else involved.

[quote user="FJR"]If there is a version available with debugoptions turned off, we may test if debug is the reason for slowing down ...[/quote]

Sorry, not available.

<p>[quote user="FJR"]May that be the reason for slowed down filteringspeed (SPAMhalter and self created filters) in factor three on new mails? We used PM451 before and the admins tested PM461 for a while. Because we thought, the differences are not that big we decided to have a rollout with PM463. Last Friday my colleague had a test on his real mailbox with about 200 mails in inbox ... and screemed about slowed filtering.[/quote]</p><p>I don't know, after all it's only a guess, and if it only affects a single user there may very well be something else involved.</p><p>[quote user="FJR"]If there is a version available with debugoptions turned off, we may test if debug is the reason for slowing down ...[/quote]</p><p>Sorry, not available.</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

OK - on slow opening - checking new mail - Pegasus is using 47-48% CPU according to Win XP Task Manager.  I notice the Icons at the top refreshing slowly - take a fraction of a second to paint each one.  Used to be near instantaneous.

OK - on slow opening - checking new mail - Pegasus is using 47-48% CPU according to Win XP Task Manager.  I notice the Icons at the top refreshing slowly - take a fraction of a second to paint each one.  Used to be near instantaneous.

[quote user="ArtM"]OK - on slow opening - checking new mail - Pegasus is using 47-48% CPU according to Win XP Task Manager.  I notice the Icons at the top refreshing slowly - take a fraction of a second to paint each one.  Used to be near instantaneous. [/quote]

Sure, reading and filtering 9000 messages certainly slows down processing. And POP3 or SMTP processing always raises CPU usage, this hasn't changed recently, only drawing

graphics

has been reworked with the introduction of the new bitmaps.

<p>[quote user="ArtM"]OK - on slow opening - checking new mail - Pegasus is using 47-48% CPU according to Win XP Task Manager.  I notice the Icons at the top refreshing slowly - take a fraction of a second to paint each one.  Used to be near instantaneous. [/quote]</p><p>Sure, reading and filtering 9000 messages certainly slows down processing. And POP3 or SMTP processing always raises CPU usage, this hasn't changed recently, only drawing graphics has been reworked with the introduction of the new bitmaps.</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

> OK - on slow opening - checking new mail - Pegasus is using 47-48% CPU
> according to Win XP Task Manager.  I notice the Icons at the top
> refreshing slowly - take a fraction of a second to paint each one.
> Used to be near instantaneous.

Have you tried:

1.    Turning off Spamhalter?

2.    Turning off content control?

3.    Moving about 8800 of the 9000 messages in the new mail folder to another folder, especially any huge messages that take a long time to scan.

> OK - on slow opening - checking new mail - Pegasus is using 47-48% CPU > according to Win XP Task Manager.  I notice the Icons at the top > refreshing slowly - take a fraction of a second to paint each one. > Used to be near instantaneous. Have you tried: 1.    Turning off Spamhalter? 2.    Turning off content control? 3.    Moving about 8800 of the 9000 messages in the new mail folder to another folder, especially any huge messages that take a long time to scan.

Re :  reading and filtering 9000 messages certainly slows down processing

 

Yes - have tried moving/marking to Main before & helps speed.  But this is situation where time to open has gone from 2-5 mins to 15-20+ mins

<p>Re :  reading and filtering 9000 messages certainly slows down processing</p><p> </p><p>Yes - have tried moving/marking to Main before & helps speed.  But this is situation where time to open has gone from 2-5 mins to 15-20+ mins </p>

- Turned off Spamhalter (thought it was already off ?? Does this default to activated on 4.63 ?

- I have a relatively short list of input filters to colorize, etc.

Tried moving many msgs from New to Main.  Stopped on error "Main can't be bigger than  2 GB"  No way out.  Had to kill PEG with Task mgr.  PEG has restarted OK & msgs that moved OK.

<p>- Turned off Spamhalter (thought it was already off ?? Does this default to activated on 4.63 ? - I have a relatively short list of input filters to colorize, etc. </p><p>Tried moving many msgs from New to Main.  Stopped on error "Main can't be bigger than  2 GB"  No way out.  Had to kill PEG with Task mgr.  PEG has restarted OK & msgs that moved OK. </p>

I'm not shure about the 2GB-limit ... may be somebody else knows ... but finally there will be a limit by OS - which ever.

Anyway ... perhaps you should create a tray "archive" with folders one per year in. With closed Pegasus backup PMM- and PMI-file of main folder (have a look at folderinformation in contextmenue of folder), check consistency of main folder, reindex it if necessary and move mails per year to the yearly folder. If Pegasus doesn't compress the folder automatically after each yearly move (you have to click to another folder once), do it via contextmenue. That's what I do especially with folders where mails go by filtering.

bye   Olaf

 

<p>I'm not shure about the 2GB-limit ... may be somebody else knows ... but finally there will be a limit by OS - which ever. </p><p>Anyway ... perhaps you should create a tray "archive" with folders one per year in. With closed Pegasus backup PMM- and PMI-file of main folder (have a look at folderinformation in contextmenue of folder), check consistency of main folder, reindex it if necessary and move mails per year to the yearly folder. If Pegasus doesn't compress the folder automatically after each yearly move (you have to click to another folder once), do it via contextmenue. That's what I do especially with folders where mails go by filtering.</p><p>bye   Olaf</p><p> </p>

[quote user="FJR"]

I'm not shure about the 2GB-limit ... may be somebody else knows ... but finally there will be a limit by OS - which ever.

 [/quote]

Has been discussed previously. 32 bit hardware architectural limitation.

[quote user="FJR"]<p>I'm not shure about the 2GB-limit ... may be somebody else knows ... but finally there will be a limit by OS - which ever. </p><p> [/quote]</p><p>Has been discussed previously. 32 bit hardware architectural limitation. </p>

I thought I had this problem whipped.  But last night it reared its head again.  Took 45 mins to close Pegasus.
Previously in the session it had been very sluggish in most mail tasks.

I previously have turned off all spam filtering.  However I still have end of session filtering to move read mail to various senders folders.
This has not been a problem all along.  I also purged Main folder back to abt 50K messages some time ago.

 I thought it might be a 'runaway' script in a tab in Firefox.  So I closed them one by one & watched Windows XP Task Manager processes CPU.
No FF tabs affected total CPU that much.  I closed FF & most other tasks.  None affected situation.

But Pegasus stubbornly sat at about 49% CPU until it finally finished !  Priority Normal.  51% sat on the Idle Process.

The Pegasus memory showed 75MB.  but this should be OK on a 4GB system.  Free memory showed over 2GB.

Today it seems fine.

I'm lost again !!

<p>I thought I had this problem whipped.  But last night it reared its head again.  Took 45 mins to close Pegasus. Previously in the session it had been very sluggish in most mail tasks. </p><p>I previously have turned off all spam filtering.  However I still have end of session filtering to move read mail to various senders folders. This has not been a problem all along.  I also purged Main folder back to abt 50K messages some time ago.</p><p> I thought it might be a 'runaway' script in a tab in Firefox.  So I closed them one by one & watched Windows XP Task Manager processes CPU. No FF tabs affected total CPU that much.  I closed FF & most other tasks.  None affected situation. </p><p>But Pegasus stubbornly sat at about 49% CPU until it finally finished !  Priority Normal.  51% sat on the Idle Process. </p><p>The Pegasus memory showed 75MB.  but this should be OK on a 4GB system.  Free memory showed over 2GB.</p><p>Today it seems fine. </p><p>I'm lost again !! </p>

[quote user="ArtM"]I thought I had this problem whipped.  But last night it reared its head again.  Took 45 mins to close Pegasus.

Previously in the session it had been very sluggish in most mail tasks.[/quote]

Try setting Tools => Options => Advanced settings => Load Windows Internet Services ... to Always and restart Pegasus Mail.

[quote user="ArtM"]I thought I had this problem whipped.  But last night it reared its head again.  Took 45 mins to close Pegasus. <p>Previously in the session it had been very sluggish in most mail tasks.[/quote]</p><p>Try setting <em>Tools => Options => Advanced settings => Load Windows Internet Services ...</em> to <em>Always</em> and restart Pegasus Mail.</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

RE "Try setting Tools => Options => Advanced settings => Load Windows Internet Services ... to Always and restart Pegasus Mail."
Been there.  Done that.  Long ago.

I noticed one thing while in that Advanced Settings box though;
I at some time I must have set the 'Recovery of Deleted Space' to compact once 50,000 bytes deleted.
Given I get a fair amount of mail; and some of it gets moved to specified folders on Pegasus exit;
does this mean that potentially my New Mail folder gets compacted whenever, any amount of e-mail
totalling over 50,000 bytes gets moved out of it ?  This potentially can explain the slow closing; if true.


It Does Not explain just plain sluggish normal operation reading mail, switching between folders, etc.

 

<p>RE "Try setting <em>Tools => Options => Advanced settings => Load Windows Internet Services ...</em> to <em>Always</em> and restart Pegasus Mail." Been there.  Done that.  Long ago.</p><p>I noticed one thing while in that Advanced Settings box though; I at some time I must have set the 'Recovery of Deleted Space' to compact once 50,000 bytes deleted. Given I get a fair amount of mail; and some of it gets moved to specified folders on Pegasus exit; does this mean that potentially my New Mail folder gets compacted whenever, any amount of e-mail totalling over 50,000 bytes gets moved out of it ?  This potentially can explain the slow closing; if true.</p><p> It Does Not explain just plain sluggish normal operation reading mail, switching between folders, etc. </p><p> </p>

[quote user="ArtM"]It Does Not explain just plain sluggish normal operation reading mail, switching between folders, etc. [/quote]

Do you have an (unconnected) network printer set as Windows default printer?

<p>[quote user="ArtM"]It Does Not explain just plain sluggish normal operation reading mail, switching between folders, etc. [/quote]</p><p>Do you have an (unconnected) network printer set as Windows default printer?</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

No network printer as default - only USB.

I do have an IEEE 1394 connection to a scanner - but this is seldom used & powered on.

 

<p>No network printer as default - only USB.</p><p>I do have an IEEE 1394 connection to a scanner - but this is seldom used & powered on.</p><p> </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft