[contestms] Re: CMS has been used

  • From: "Pevec, Darko" <Darko.Pevec@xxxxxxxxxxxxx>
  • To: "<contestms@xxxxxxxxxxxxx>" <contestms@xxxxxxxxxxxxx>
  • Date: Sun, 26 May 2013 12:48:22 +0000

Hi Gio,

You must be right. I didn't fiddle with the configuration file and only changed 
what was necessary.
I believe the default should be set to false because it really does eat space 
up at a surprising rate.
Thinking about it, the admin web could be extended to be able to display 
contestants outputs, not only the submitted code.

On May 26, 2013, at 13:57, "Giovanni Mascellani" 
<mascellani@xxxxxxxxxxxxxxxxxxxx> wrote:

> Hi Darko.
> 
> Il 26/05/2013 11:54, Pevec, Darko ha scritto:
>> There were no real problems, the system worked like a charm. But when
>> you're already mentioning it, I naively set "only" 10gb of disk space
>> for the virtual competition server and in the middle of our first
>> competition ran out of disk space :) I have to ask why does the
>> system use up sooo much disk space? I have the feeling that
>> everything gets cached at least three times and then nothing gets
>> cleaned up. We were using a now obsolete version so I hope this
>> recieved some attention. At least give a heads up to people who are
>> trying the CMS for the first time.
> 
> As Luca said, I think the problem is probably that you used keep_sandbox
> = true, which eats space really quickly. (@cms-dev: why is it on by
> default? Couldn't we disable it by default?)
> 
> Caching is too a bit underoptimized, we could work on it (this requires
> a bit of care to prevent race conditions, but it shouldn't be too
> difficult; the point, as Luca said, is that so far this has never been
> an issue to us).
> 
>>> BTW, usual question: any problem if we add your contests to the
>>> list of testimonials?
>> 
>> Of course not, that was my original intent.
> 
> Added!
> 
> Gio.
> -- 
> Giovanni Mascellani <mascellani@xxxxxxxxxxxxxxxxxxxx>
> Pisa, Italy
> 
> Web: http://poisson.phc.unipi.it/~mascellani
> Jabber: g.mascellani@xxxxxxxxxx / giovanni@xxxxxxxxxxxxxxxxxxxx
> 

Other related posts: