[squeak-dev] The Trunk: Graphics-mt.482.mcz
Christoph.Thiede at student.hpi.uni-potsdam.de
Thu Feb 24 22:23:50 UTC 2022
just two notes from my side, but no clear opinion here. :-)
> I assume that the user can spare those extra megs on disk while working.
On my main machine, I have 233 .image files with 28 GB in total. So maybe "those extra megs" could indeed be relevant ... But I did not do a rough calculation. :-)
> Which server images save on a regular basis? :-D
The image for https://t.me/SqueakSmalltalkBot does, once in ten minutes. Will this increase the wear and tear of my raspi's SD card? :-) To be honest, I would prefer it if "Smalltalk snapshot: ... andQuit: ..." would support the server use case out-of-the-box, too, without extra scripting. But if we are only talking about a few kilobytes here, I don't mind. :-)
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel
Gesendet: Mittwoch, 16. Februar 2022 17:26:38
Betreff: Re: [squeak-dev] The Trunk: Graphics-mt.482.mcz
Hi Tim --
> The problem here is image file bloating
I know. Is this a problem? I assume that the user can spare those extra megs on disk while working. Yet, it is annoying to get a stuttering system after snapshotting, which might even encourage people to not save that often.
> It should start ok but might be a problem for server cases where startup time is important?
Which server images save on a regular basis? :-D You can always call "Form shutdown: true" and "TTCFont shutdown: true" in your server scripts directly before snapshotting ... I assume that servers have such scripts anyway and those two extra lines wouldn't hurt...
Am 14.02.2022 18:29:21 schrieb tim Rowledge <tim at rowledge.org>:
> On 2022-02-14, at 8:43 AM, Marcel Taeumel wrote:
> Hi all --
> Please report whether I am overlooking something here... It was kind of annoying that my entire TrueType cache was gone after just saving the image and keep on working.
The problem here is image file bloating; the hibernation is intended to save (quite a bit of) space in the image file. If we only hibernate when save&quitting then we will see patterns in the snapshot file size like
.. which maybe wouldn't bother anyone, maybe would annoy some?
Also, a few save-no-quits followed by a damn-I-broke-it-quit-no-save would lave the large file as the one you have to start up. It should start ok but might be a problem for server cases where startup time is important?
High-tech-insane solution - use DTL's spawn-an-image and have that image do the hibernate & save! Couldn't possibly go wrong...
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: CM: Circulate Memory
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev