And⦠for those who do not understand the code names: - Aleph is an index system that keeps senders/implementors and references, making access to this queries almost automatic even in very big images. - This also speeds up all refactors, since they query for implementors and references all the time. - Spotter queries have been redesigned to not create the full list before showing it, but fetching the values using a generator. It also uses aleph (which in time uses a trie three) to fetch the results. Fuzzy matcher is gone here, but the gain is bigger than the lost. - Complishion is a new code completion framework who fetches also using generators, and also uses different heuristics to provide more âcloseâ answers instead just the list. Then, there is a not-so-small list of smaller changes, most of them applied directly to the image (but for those you need P9). In sum, we have speed up a lot the usage of Pharo in big images⦠but of course we will be waiting for feedback to go farther where needed :) Esteban
On 23 Mar 2020, at 10:29, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 23 Mar 2020, at 10:28, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote:
Hi,
On 23 Mar 2020, at 10:14, Vincent Blondeau via Pharo-dev <pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote:
From: "Vincent Blondeau" <vincent.blondeau@lifeware.ch <mailto:vincent.blondeau@lifeware.ch>> Subject: RE: [Pharo-dev] [Mm10] 2020-03-23 (WAS: No subject) Date: 23 March 2020 at 10:14:12 CET To: "'Pharo Development List'" <pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org>>
Hi Pablo,
Great news! We are eager to test this. Do you plan to backport the changes for the large images to Pharo8.0? Or should we try a 9.0 to try it?
While there is no reason that aleph (and complishion) would not work on P8, for some more subtle changes you will need to jump on P9 (but no worries, P9 it is very stable) :) And spotter :P
Esteban
Also, what is Aleph? (I cannot find a description in this list thread...)
Cheers, Vincent Blondeau Lifeware SA
-----Original Message----- From: Pharo-dev On Behalf Of tesonep@gmail.com <mailto:tesonep@gmail.com> Sent: Monday, 23 March 2020 10:02 To: Pharo-dev <pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> Subject: Re: [Pharo-dev] (no subject)
Sorry for the subject less message, sending it too fast
On Mon, Mar 23, 2020 at 9:55 AM tesonep@gmail.com <mailto:tesonep@gmail.com> <tesonep@gmail.com <mailto:tesonep@gmail.com>> wrote:
Monday morning, so I spam to tell what I have done last week for Pharo.
### Last week:
- Integrating Spotter processors with Aleph - Testing problem with Pharo8 and Metacello loading. - Debugging problem with SDL in OSX Pharo8 VM - Adding classes indexes to AlephIndexManager - Adding a baseline to load Spotter + Aleph + Completion: this improves the spotter/completion and senders/implementors/... for large images. An announcement will arrive when I have better index generation times. - Generating a Big image for testing (using github.com/tesonep/pharo-image <http://github.com/tesonep/pharo-image> generator) - Commenting and fixing PR - Deleting closed PR from Jenkins - A new version of the VM for RHEL (32 / 64 bits) - Improving the performance of the indexes of Spotter
### This week... idealy (starting 2020-03-23):
- Improving Large images index generation time. - Fixing Package List / Categories in Calypso - [VM] Fix symbolic links in Pharo8 VM - Adding a label to a PR when it has no test errors. - [OSSubprocess] Integrate Pavel + Christophe windows version. - [VM] Check the crash dumps in an endless loop - [VM] Improve the usage of Stdout and Stderr, in a correct way - [Pharo9] Propose a PR for Fuel to support Sista - [VM] Fixing Tests in Idle. - [VM] SDL Plugin for Idle. - [VM] Improving Speed of TFFI. - [VM] Writing tests for JIT generation
-- Pablo Tesone. tesonep@gmail.com <mailto:tesonep@gmail.com>
-- Pablo Tesone. tesonep@gmail.com <mailto:tesonep@gmail.com>