2GB was the per-process memory limit in Mac OS X 10.2 and earlier. 10.3
increased this to 4GB per-process. I've gotten MySQL running with 3GB
of RAM on the G5 previously.
This is an excerpt from a prior email to the list from back in October
when I was first testing MySQL on the G5:
> query_cache_size=1024M
> bulk_insert_buffer_size=256M
> tmp_table_size=128M
> sort_buffer=8M
> read_rnd_buffer_size=8M
> key_buffer=768M
> record_buffer=32M
> myisam_sort_buffer_size=512M
> innodb_buffer_pool_size=1024M
> innodb_additional_mem_pool_size=32M
> However, for some reason, when I swapped the values key_buffer and
query_cache_size to try and give
> key_buffer 1GB, it failed. I swapped the values back and it worked
fine... odd.
- Gabriel
On Jan 26, 2004, at 11:16 AM, Brent Baisley wrote:
> Yes, MySQL is capable of using more than 2GB, but it still must obey
> the limits of the underlying OS. This means file sizes, memory
> allocation and whatever else. Have you heard of anybody allocating
> more the 2GB using OSX? I've heard of quite a bit more using Linux or
> other Unix flavors, but not OSX.
>
> As for optimizing settings, you need to profile you work load. You may
> actually run into I/O, CPU or Network bottleneck before you hit a
> memory bottleneck. You need to run things and find where the
> bottleneck is to optimize performance.
>
> On Jan 26, 2004, at 11:09 AM, Adam Goldstein wrote:
>
>> Others on this list have claimed to be able to set over 3G, and my
>> failure is with even less than 2G (though, I am unsure if there is a
>> combination of other memory settings working together to create an
>> >2GB situation combined)
>>
> --
> Brent Baisley
> Systems Architect
> Landover Associates, Inc.
> Search & Advisory Services for Advanced Technology Environments
> p: 212.759.6400/800.759.0577
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=1
>
