On Thu, Mar 8, 2012 at 1:04 PM, Jack O'Quin <firstname.lastname@example.org> wrote: > On Thu, Mar 8, 2012 at 12:54 PM, Ken Conley <email@example.com> wrote:
>> As many noticed, the ROS wiki had some uptime issues in recent weeks.
>> We have tracked this down to inefficiencies with MoinMoin's attachment
>> system. While we have removed the top causes of the instability, this
>> is likely to crop up again with continued use. We ask that you avoid
>> using attachments on the ROS wiki as much as possible. In most cases
>> where we have seen attachments, the file could have easily instead
>> been offered from a source code repository. For example, rosinstall
>> files and source code examples are much more easily maintained within
>> a source control system.
>> We cannot disable this feature without removing existing attachments,
>> so we ask for your help in reducing the load on the server. In the
>> case of particular attachments that are causing issues, you may
>> receive e-mails to ask you to remove the attachment.
> Are there particular types of attachments to watch out for?
Anything that ends up getting a lot of hits will be problematic.
Images require extra processing, but the page that really hurt the
wiki was serving up code. MoinMoin simply isn't that efficient
serving attachments, so we shouldn't think of it like a fileserver.
Obviously, there are lots of useful diagrams and other
documentation-related items that we don't want to get rid of, and we
don't want to make it difficult to contribute content. That said, as
most people contributing wiki content have access to a source control
system, this is generally a call to those users to use those source
control systems instead where it makes sense (e.g. rosinstall files
and code files). Documentation can also be written using
doxygen/sphinx/etc... and still be viewable on ROS.org via rosdoc, so
that is another alternative.