On Fri, 25 May 2012, Bert Freudenberg wrote:

>
> On 24.05.2012, at 00:43, Chris Cunningham wrote:
>
>> On Wed, May 23, 2012 at 10:28 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>> Accessing the repository gets slower and slower due to the ever increasing number of versions there.
>>>
>>> To make it faster we could remove old package versions. Say, everything older than a year (but keep at least one version of each package). We could move those to an "attic" repository.
>>>
>>> Sounds good? Other ideas?
>>>
>>> - Bert -
>>
>> When you need the configuration file to load specific versions of
>> packages, I would assume we'd want to keep those versions.
>> Also, are you considering removing those configuration files as well?
>>
>> -Chris C (not Cunnington)
>
> Good question, and a potential obstacle.
>
> I think the simplest solution would be to not move the update configs over. Instead, rewrite them on the server to have both the trunk and attic repositories. (a config stores the repositories where it is looking for packages).
>
> OTOH, we now have more than 200 configs in trunk, and they, too, slow down the repository listing.
>
> Maybe we need something similar to the MCD generation: If the image lets the server know which updates it already knows about, the server would only have to send newer ones.

I think the best solution to the problem would be to add a new "view" (a 
pseudo project/repository) to the SqueakSource server, which would show 
only a limited amount of packages. E.g.: 
http://source.squeak.org/trunk/recent would only list recently added 
packages and configurations, while 
http://source.squeak.org/trunk would show the full list.
Saving to the pseudo repository would have the same effect as saving to 
the main one.


Levente

>
> - Bert -
>
>
>
>