[Glass] Loading application time via Gofer or directly via topaz

Dale Henrichs dale.henrichs at gemtalksystems.com
Wed Mar 2 08:55:43 PST 2022

Without detailed information about the errors and testing scenarios,
there's not much that I can say, other than if .gs files are working for
you, then by all means use them ...

Monticello and git tends to become more useful when you are sharing code
across multiple platforms and multiple developers. Arranging for
conditional loading with topaz files can be cumbersome and depending upon
how you organize the topaz files, merging of changes from multiple users
can also be tedious  ...

it turns out that filetree (one file per method) greatly simplifies git
merges, whereas large class tonel files can suffer from the same problems
that large .gs files when it comes to merging changes. For Rowan I am
considering adding support for custom merge drivers
ala GitFileTree-MergeDriver[1] ... GitFileTree-MergeDriver was created to
automerge the Monticello properties files, which were a constant headache
for filetree when Monticello metadata was present.


[1] https://github.com/ThierryGoubier/GitFileTree-MergeDriver

On Wed, Mar 2, 2022 at 1:16 AM Marten Feldtmann via Glass <
glass at lists.gemtalksystems.com> wrote:

> Hey,
> so I decided to go away from Monticello packages for these very large
> source code files and switch to pure topaz code - the process does not seem
> to be reliable when the stuff is getting too large. I had to reinstall
> Gemstone database and got again the same problems - topaz code is loading
> much faster and the loading has ever worked ...
> Marten
> Marten Feldtmann via Glass <glass at lists.gemtalksystems.com> hat am
> 27.02.2022 18:25 geschrieben:
> Hey,
> I am currently working with Gemstone/S 3.6.3 and today I had lots of
> problems, loading large software packages via Gopher - the topaz process
> (using Gopher) got killed (as it seems) by the operating system when
> loading the software, no message and the putty session got killed also.
> I am heavily model based working, so the complete domain model, the API
> model and APIs itselfs, the OpenAPI specification, the documentation are
> generated in Smalltalk source code. My - by far - largest application
> produces 18 MByte of source code (topaz-pure code).
> The generator generates topaz source code (18 MB) which is normally loaded
> once  and then (from within Jade) I produce a Monticello package (3.6 MB)
> and for further work I use these Monticello packages.
> Today I measured the loading time: 6 minutes (topaz) against 24 minutes
> (monticello) on the same machine - I assume, that a git based solution will
> not be much better, perhaps even worse ?
> Just for your information purposes ....
> _______________________________________________ Glass mailing list
> Glass at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/glass
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/glass
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20220302/7dbf110d/attachment.htm>

More information about the Glass mailing list