You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: iknopf [Submitted to the original trac issue database at 9.59pm, Sunday, 11th April 2010]
In tilesAtHome.conf is the key "RenderStripes" commented out by default.
When my client rendered tile 12/1025/1694, the rendering took 8 GByte of physical and 8 GByte of virtual Memory (64bit,Fedora11). This was much too much for my PC, after 2 hours I had to reset the computer. After this I tried it again with al value of "RenderStripes = 5", and everything worked fine.
Well, I do not know what type of maschines all the other users have; but the project is named "tiles@home"'' and not ''"tiles@theServersOfMyCompany". And so I suggest to set "RenderStripes = 5" by default and to change the corresponding description.
The text was updated successfully, but these errors were encountered:
Reporter: iknopf
[Submitted to the original trac issue database at 9.59pm, Sunday, 11th April 2010]
In
tilesAtHome.conf
is the key "RenderStripes
" commented out by default.When my client rendered tile 12/1025/1694, the rendering took 8 GByte of physical and 8 GByte of virtual Memory (64bit,Fedora11). This was much too much for my PC, after 2 hours I had to reset the computer. After this I tried it again with al value of "
RenderStripes = 5
", and everything worked fine.Well, I do not know what type of maschines all the other users have; but the project is named "tiles@home"'' and not ''"tiles@theServersOfMyCompany". And so I suggest to set "
RenderStripes = 5
" by default and to change the corresponding description.The text was updated successfully, but these errors were encountered: