Bug #24757 No way to limit memory consumption of some server subsystems.
| Submitted: | 1 Dec 2006 15:21 | Modified: | 1 Dec 2006 20:01 |
|---|---|---|---|
| Reporter: | Konstantin Osipov (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S4 (Feature request) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any |
[1 Dec 2006 15:21]
Konstantin Osipov
[1 Dec 2006 20:01]
Sveta Smirnova
Thank you for the reasonable feature request.
[14 Sep 2008 15:55]
Valeriy Kravchuk
Bug #39442 was marked as a duplicate of this one.
[10 Jan 2009 2:57]
Chris Calender
Other suggestions in addition to the above: user-based or process-based Solaris10 groups would be welcome ... (i.e., project / user_attr / exec_attr, or newtask / projects / prctl / rctladm).
[10 Jan 2009 5:20]
Shane Bester
Something that might help some folks, is a little know option of mysqld: If you want to be sure no users are allocating per-session buffers too high, you may start the server with options: --maximum-sort_buffer_size=5M --maximum_read_buffer_size=2M --maximum_tmp_table_size=5M etc .... In the above cases, this limits session values to the specified limits.
[28 Feb 2009 15:29]
Peter Gulutzan
WL#3824
[28 Jan 2014 17:59]
Sveta Smirnova
Bug #71497 was marked as duplicate of this one.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.064 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.