On Fri, Apr 11, 2008 at 2:20 AM, Jürgen Keil <[EMAIL PROTECTED]> wrote:
> And another case was an attempt to use "xsltproc(1)" on a
> big xml file, this time on an amd64 x2 machine with 4GB of
> memory, using zfs, and the xsltproc process had grown to
> use > 2GB of memory. Again heavy disk tr
Jason,
> Hi Jurgen,
>
> On our Thumpers running MySQL, we limit the ARC to 4GB.
> On systems with less RAM we limit the ARC to 1GB.
Ok, on a machine running a database server (and nothing else),
that might make sense.
On a general purpose box it doesn't make much sense;
I'd have to reboot the b
Brandon wrote:
> On Fri, Apr 11, 2008 at 12:21 PM, Jürgen Keil <[EMAIL PROTECTED]> wrote:
> > > And another case was an attempt to use "xsltproc(1)" on a
> > > big xml file, this time on an amd64 x2 machine with 4GB of
> > > memory, using zfs, and the xsltproc process had grown to
> > > use > 2
Hi Jurgen,
On our Thumpers running MySQL, we limit the ARC to 4GB. On systems
with less RAM we limit the ARC to 1GB. What kind of disk is backing
the pools? Might be some kind of array cache flushing issues going on.
Also, you might try putting your InnoDB log files on a UFS partition
and see if t
On Fri, Apr 11, 2008 at 12:21 PM, Jürgen Keil <[EMAIL PROTECTED]> wrote:
> > And another case was an attempt to use "xsltproc(1)" on a
> > big xml file, this time on an amd64 x2 machine with 4GB of
> > memory, using zfs, and the xsltproc process had grown to
> > use > 2GB of memory. Again heavy
> And another case was an attempt to use "xsltproc(1)" on a
> big xml file, this time on an amd64 x2 machine with 4GB of
> memory, using zfs, and the xsltproc process had grown to
> use > 2GB of memory. Again heavy disk trashing, and I
> didn't had the impression that the arc cache did
> shrink e
On Fri, Apr 11, 2008 at 2:20 AM, Jürgen Keil <[EMAIL PROTECTED]> wrote:
> According to the source, it's "3/4 of all memory, or all but 1G,
> whichever is more" (64-bit kernel only, 32-bit is different).
For some reason 1/2 stuck in my head as the max, but I'll believe you. :-)
> 1GB. The resu
Brandon wrote:
> On Thu, Apr 10, 2008 at 12:59 AM, Nico Sabbi <[EMAIL PROTECTED]> wrote:
> > yes, I limited the ARC only after having verified that the default
> > setting (unspecified in /etc/system) was too slow.
> > What would be a good value considering that the server has 2 GB
> > of ram?
On Thu, Apr 10, 2008 at 12:59 AM, Nico Sabbi <[EMAIL PROTECTED]> wrote:
> yes, I limited the ARC only after having verified that the default
> setting (unspecified in /etc/system) was too slow.
> What would be a good value considering that the server has 2 GB
> of ram?
Without knowing the spec
On Thursday 10 April 2008 02:21:36 you wrote:
> On Sat, Apr 5, 2008 at 1:15 AM, Nico Sabbi <[EMAIL PROTECTED]>
wrote:
> > - limiting zfs's usage of memory to 256MB (appending to
> > /etc/system set zfs:zfs_arc_max = 0x800
> > and rebooting, hopefully I did the right thing)
>
> My gut reactio
On Sat, Apr 5, 2008 at 1:15 AM, Nico Sabbi <[EMAIL PROTECTED]> wrote:
> - limiting zfs's usage of memory to 256MB (appending to /etc/system
> set zfs:zfs_arc_max = 0x800
> and rebooting, hopefully I did the right thing)
My gut reaction is that you've shot yourself in the foot by making the
Il Saturday 05 April 2008 12:23:19 Lurie ha scritto:
> http://dev.mysql.com/tech-resources/articles/mysql-zfs.html
>
>
that is the first document I read, but none of the tips helped in any way.
I forgot to mention that I disabled the doublewrite, but without any improvement
___
http://dev.mysql.com/tech-resources/articles/mysql-zfs.html
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Hi,
yesterday I installed Solaris 01/08 on a Sun's server with two 2Ghz Opterons
and 2 GB ram
(I don't remember the model of the server but it's one of those 1U
rack-mountable
servers with -hideous- rocket-loud fans that never slow down, maybe VX2200 ? )
I configured the bundled Mysql 5.0.xx to
14 matches
Mail list logo
