[7.7.1] Wave's ServerMemoryPolicy issues
Locked
[7.7.1] Wave's ServerMemoryPolicy issues
 
|
1. No package should install a third-party memory policy when loaded w/o asking, Wave-Server’s post-load, [:package | VisualWave.ServerMemoryPolicy reinstallFromSettings] ServerMemoryPolicy class>>reinstallFromSettings ObjectMemory installMemoryPolicy: self new setDefaults 2. I seem to recall some comments on the list about new memory policies being suited/flexible for all kinds of applications, including web servers, which would imply that perhaps Wave’s ServerMemoryPolicy is obsolete and should be removed altogether? 3. If you restore LargeGrainMemoryPolicy, Wave will eventually break with at least the following, because it’s assuming that its own policy is the current one and call method(s) that are no longer available on new-style policy classes, Unhandled exception: Message not understood: #canAssessLoad LargeGrainMemoryPolicy(Object)>>doesNotUnderstand: VisualWave.ServerMemoryPolicy class>>currentLoad VisualWave.SecureSessionInactivityPolicy(VisualWave.SessionInactivityPolicy)>>purgeExpirees optimized [] in VisualWave.SecureSessionInactivityPolicy>>startPurgeProcess BlockClosure>>on:do: optimized [] in Process class>>forBlock:priority: Regards, -Boris -- DeepCove Labs Ltd. +1 (604) 689-0322 4th floor, 595 Howe Street Vancouver, British Columbia Canada V6C 2T5 http://tinyurl.com/r7uw4 PacNet Services (Europe) Ltd. +353 (0)61 714-360 Shannon Airport House, SFZ County Clare, Ireland http://tinyurl.com/y952amr CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [7.7.1] Wave's ServerMemoryPolicy issues
|
|
I did update Wave's memory policy settings according to the new memory
policy guidelines, so I'd expect performance to be generally improved (with the usual YMMV caveats). However, working on Wave itself was outside the scope of the memory policy improvements for 7.7.1. It seems that problem #3 would have happened with the old MemoryPolicy class as well. Apparently, it's more of an existing problem rather than a regression that occurred with 7.7.1. Andres. On 8/26/2010 3:06 AM, Boris Popov, DeepCove Labs (SNN) wrote: > 1. No package should install a third-party memory policy when loaded w/o > asking, > > > > Wave-Server's post-load, > > [:package | VisualWave.ServerMemoryPolicy > reinstallFromSettings] > > > > ServerMemoryPolicy class>>reinstallFromSettings > > ObjectMemory installMemoryPolicy: self new setDefaults > > > > 2. I seem to recall some comments on the list about new memory policies > being suited/flexible for all kinds of applications, including web > servers, which would imply that perhaps Wave's ServerMemoryPolicy is > obsolete and should be removed altogether? > > > > 3. If you restore LargeGrainMemoryPolicy, Wave will eventually break > with at least the following, because it's assuming that its own policy > is the current one and call method(s) that are no longer available on > new-style policy classes, > > > > Unhandled exception: Message not understood: #canAssessLoad > > LargeGrainMemoryPolicy(Object)>>doesNotUnderstand: > > VisualWave.ServerMemoryPolicy class>>currentLoad > > > VisualWave.SecureSessionInactivityPolicy(VisualWave.SessionInactivityPol > icy)>>purgeExpirees > > optimized [] in > VisualWave.SecureSessionInactivityPolicy>>startPurgeProcess > > BlockClosure>>on:do: > > optimized [] in Process class>>forBlock:priority: > > > > Regards, > > > > -Boris > > > > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [7.7.1] Wave's ServerMemoryPolicy issues
|
|
Andres,
It is a regression, because all memory policies used to understand #canAssessLoad prior to 7.7.1, here's a method from 7.7 which needs to be moved to AbstractMemoryPolicy in 7.7.1 to address this specific issue, MemoryPolicy>>canAssessLoad ^false Having said that, I'd still like to see it either be removed completely in favour of new policies (Q #2), or at least not be a default memory policy immediately upon loading (Q #1). Regards, -Boris -- DeepCove Labs Ltd. +1 (604) 689-0322 4th floor, 595 Howe Street Vancouver, British Columbia Canada V6C 2T5 http://tinyurl.com/r7uw4 PacNet Services (Europe) Ltd. +353 (0)61 714-360 Shannon Airport House, SFZ County Clare, Ireland http://tinyurl.com/y952amr CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Andres Valloud Sent: 26 August 2010 11:22 To: [hidden email] Subject: Re: [vwnc] [7.7.1] Wave's ServerMemoryPolicy issues I did update Wave's memory policy settings according to the new memory policy guidelines, so I'd expect performance to be generally improved (with the usual YMMV caveats). However, working on Wave itself was outside the scope of the memory policy improvements for 7.7.1. It seems that problem #3 would have happened with the old MemoryPolicy class as well. Apparently, it's more of an existing problem rather than a regression that occurred with 7.7.1. Andres. On 8/26/2010 3:06 AM, Boris Popov, DeepCove Labs (SNN) wrote: > 1. No package should install a third-party memory policy when loaded > w/o asking, > > > > Wave-Server's post-load, > > [:package | VisualWave.ServerMemoryPolicy > reinstallFromSettings] > > > > ServerMemoryPolicy class>>reinstallFromSettings > > ObjectMemory installMemoryPolicy: self new setDefaults > > > > 2. I seem to recall some comments on the list about new memory > policies being suited/flexible for all kinds of applications, > including web servers, which would imply that perhaps Wave's > ServerMemoryPolicy is obsolete and should be removed altogether? > > > > 3. If you restore LargeGrainMemoryPolicy, Wave will eventually break > with at least the following, because it's assuming that its own policy > is the current one and call method(s) that are no longer available on > new-style policy classes, > > > > Unhandled exception: Message not understood: #canAssessLoad > > LargeGrainMemoryPolicy(Object)>>doesNotUnderstand: > > VisualWave.ServerMemoryPolicy class>>currentLoad > > > VisualWave.SecureSessionInactivityPolicy(VisualWave.SessionInactivityP > ol > icy)>>purgeExpirees > > optimized [] in > VisualWave.SecureSessionInactivityPolicy>>startPurgeProcess > > BlockClosure>>on:do: > > optimized [] in Process class>>forBlock:priority: > > > > Regards, > > > > -Boris > > > > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [7.7.1] Wave's ServerMemoryPolicy issues
|
|
Ahh, I see what you mean now. Oops :(.
On 8/26/2010 3:27 AM, Boris Popov, DeepCove Labs (SNN) wrote: > Andres, > > It is a regression, because all memory policies used to understand > #canAssessLoad prior to 7.7.1, here's a method from 7.7 which needs to > be moved to AbstractMemoryPolicy in 7.7.1 to address this specific > issue, > > MemoryPolicy>>canAssessLoad > ^false > > Having said that, I'd still like to see it either be removed completely > in favour of new policies (Q #2), or at least not be a default memory > policy immediately upon loading (Q #1). > > Regards, > > -Boris > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [7.7.1] Wave's ServerMemoryPolicy issues
|
|
In reply to this post by Boris Popov, DeepCove Labs (SNN)
61021: "Wave should refine AbstractMemoryPolicy, rather than MemoryPolicy"
On 8/26/2010 3:27 AM, Boris Popov, DeepCove Labs (SNN) wrote: > Andres, > > It is a regression, because all memory policies used to understand > #canAssessLoad prior to 7.7.1, here's a method from 7.7 which needs to > be moved to AbstractMemoryPolicy in 7.7.1 to address this specific > issue, > > MemoryPolicy>>canAssessLoad > ^false > > Having said that, I'd still like to see it either be removed completely > in favour of new policies (Q #2), or at least not be a default memory > policy immediately upon loading (Q #1). > > Regards, > > -Boris > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
«
Return to VisualWorks
|
1 view|%1 views
| Free forum by Nabble | Edit this page |