On March 4 2011, Seb35 wrote:
> Fri, 04 Mar 2011 03:45:53 +0100, MZMcBride <z...@mzmcbride.com> wrote:
>> Seb35 wrote:
>>> I'm from the French chapter and we need sometimes a lot of CPU power
>>> and/or a lot of memory for some projects. For now it happened two  
>>> times:
>>
>> It's difficult to know what "a lot" of CPU power or memory is from  
>> your
>> post. Toolserver accounts have account limits
>> (<https://wiki.toolserver.org/view/Account_limits>), so if you're  
>> staying
>> within those limits, there's generally no problem. If you want to  
>> exceed
>> those limits, you should talk to the Toolserver roots first
>> (<https://wiki.toolserver.org/view/System_administrators>). There are
>> places
>> like /mnt/user-store that can be used for large media storage as  
>> well.
>>
>> As always, the Toolserver resources that you use need to relate to
>> Wikimedia
>> in some way, but it sounds like both of your projects do. :-)
>>
>> MZMcBride
> Ok, thank you, I didn't find this page.
>
> For the BnF project we needed in fact about one day of computation  
> (most
> of the time was used by the disk accesses), but we thought it would be
> more (we optimized too by using SAX instead of DOM to read big XML  
> files,
> it used too much memory with DOM too).
> For the video encoding to OGV (it's not me who done that), it was 4-5
> hours for a single video but some time was used to swap (and there  
> are 100
> videos corresponding to the conferences).
>
> Thank you for the response.
> Seb35

Hi Seb35,

"One day" or "4-5 hours" still don't mean a lot in terms of technical  
requirements.
One day of computing with what equipment ? With 24 hours of runtime a  
small
difference can make a big difference. What kind of server server/setup  
did this run
on ?

How much is "too much memory" ?

--
Krinkle

_______________________________________________
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Reply via email to