Hi Jason,
Depending on which hardware architecture you're working on, you may be
able to get Studio 11 compiled binaries through the CoolStack project:
http://cooltools.sunsource.net/coolstack/index.html
Regardless, optimized compiler flags for MySQL with Studio 11 are in the
source bundle listed there. If you need additional help, let me know.
Separately, it's my understanding that ZFS reduces it's memory usage as
Solaris needs to allocate more memory for applications. I've not seen
this problem but I suspect it'd be better to try to come up with a more
simple test case that mimics MySQL (i.e. mmap() or malloc through
whichever memory library MySQL is using). I suspect it's mmap or DISM,
but if it's a *alloc problem, you may want to look at the man page for
umem_debug, as that may be able to help you find where the problem is
coming from.
In fact, CoolStack may be a good tested, stable build for you to use
alongside ZFS. You can email me directly with any issues you run into
with it and I'll get it into the right group of people.
Hope that helps,
- Matt
Sanjeev Bagewadi wrote:
Jason,
Apologies.. I missed out this mail yesterday...
I am not too familiar with the options. Someoen else will have to
answer this.
Thanks and regards,
Sanjeev.
Jason J. W. Williams wrote:
Sanjeev,
Could you point me in the right direction as to how to convert the
following GCC compile flags to Studio 11 compile flags? Any help is
greatly appreciated. We're trying to recompile MySQL to give a
stacktrace and core file to track down exactly why its
crashing...hopefully it will illuminate if memory truly is the issue.
Thank you very much in advance!
-felide-constructors
-fno-exceptions -fno-rtti
Best Regards,
Jason
On 1/7/07, Sanjeev Bagewadi <[EMAIL PROTECTED]> wrote:
Jason,
There is no documented way of limiting the memory consumption.
The ARC section of ZFS tries to adapt to the memory pressure of the
system.
However, in your case probably it is not quick enough I guess.
One way of limiting the memory consumption would be limit the arc.c_max
This (arc.c_max) is set to 3/4 of the memory available (or 1GB less
than
memory available).
This is done when the ZFS is loaded (arc_init()).
You should be able to change the value of arc.c_max through mdb and set
it to the value
you want. Exercise caution while setting it. Make sure you don't have
active zpools during this operation.
Thanks and regards,
Sanjeev.
Jason J. W. Williams wrote:
> Hello,
>
> Is there a way to set a max memory utilization for ZFS? We're trying
> to debug an issue where the ZFS is sucking all the RAM out of the
box,
> and its crashing MySQL as a result we think. Will ZFS reduce its
cache
> size if it feels memory pressure? Any help is greatly appreciated.
>
> Best Regards,
> Jason
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
--
Solaris Revenue Products Engineering,
India Engineering Center,
Sun Microsystems India Pvt Ltd.
Tel: x27521 +91 80 669 27521
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
--
Matt Ingenthron - Web Infrastructure Solutions Architect
Sun Microsystems, Inc. - Client Solutions, Systems Practice
http://blogs.sun.com/mingenthron/
email: [EMAIL PROTECTED] Phone: 310-242-6439
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
