c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <799678@xxxxxxxxxxxxxxxxxx>]

Hello Nick,

Thank you for taking the time to suggest this improvement and providing
the corresponding patch!

Usually, we tend to avoid adding more configuration options on top of the existing ones, as there are already too many options.
In this particular case, setting the process limits (in terms of memory or CPU or anything) is normally something done at the operating system level  by the system administrator, rather than relying on custom options provided by each process.

Your patch may however be useful to other people who may need a quick
solution, so let's make it a Wishlist bug that other will be able to
find.

BTW, in the future, we plan to provide a greatly streamlined startup
script for OpenERP server, which will only have a few lines using the
new "openerp" module, and will allow easy customization.

Thanks for reporting!

** Changed in: openobject-server
   Importance: Undecided => Wishlist

** Changed in: openobject-server
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/799678

Title:
  Set maximum memory usage

Status in OpenERP Server:
  Won't Fix

Bug description:
  It's possible to construct stupid requests which cause memory to run
  away, and potentially crash a system. It therefore is good to be able
  to specify the maximum memory usage openerp-server can use.

  Attached is a simple patch implementing this. It uses rlimit, so it's
  Linux only. It allows one to set a config option "max_mem_mb", which
  is the maximum amount of memory in MB that the server can use. If
  openerp requests more memory, the request will fail, and openerp will
  throw an error (but continue processing other requests happily).

  This is against the latest trunk of the v5 branch. I don't have any
  experience with v6, but presumably a very similar patch will work
  perfectly fine there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/799678/+subscriptions