1.
Do you have any specific problems with performance?
Because the only thing I can say generic is that these two:
innodb_buffer_pool_size = 384M
innodb_additional_mem_pool_size = 20M
could be increased a lot, up to about 80% of RAM which could mean something like this:
innodb_buffer_pool_size = 9G
innodb_additional_mem_pool_size = 200M
But that depends on how big you database actually is, because if your DB is smaller than that this setting is worthless and you should maybe focus on allowing more memory to be used for sorting or join buffers etc.
That is why it is important to say if you experience any specific problems.

2.
When you say "flushed twice per day", what do you actually mean?
That it is deleted and rebuilt or what?

3.
If you are experiencing slow insert/updates but the rest is going fast then you should change this:
innodb_flush_log_at_trx_commit = 1
to a value of 2 instead.
But if you do you should also be aware that if the server crashes then you could loose the last changes that you have performed in the database.

Comment

If it's only one table then you can keep the setting:
innodb_additional_mem_pool_size = 20M
There is no use to allow more since it will never be used.

And actually the value of 200M is very large and I want to retract that statement from my previous post. Sorry about that!

erkules:
No unfortunately I don't have a good way to calculate it.
But it doesn't really matter since the only thing that will happen if this buffer is too small is that MySQL will allocate the memory anyway but it will write error messages about it to the MySQL error log.
So if you see these errors turn up then you can just increase the setting.

Comment

The only thing I can think of would be the key_buffer already so high so innodb buffer pool could not allocate its 3G I chose.
(And having a key buffer above say 16M makes no sense in this case as I only have one table, an innodb so I will of course lower it)
What do you think?

# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=, MASTER_PORT=,
# MASTER_USER=, MASTER_PASSWORD= ;
#
# where you replace , , by quoted strings and
# by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host =
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user =
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port =
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 384M
#bdb_max_lock = 100000

Comment

Comment

You should of course lower it but I don't think that is the problem because this buffer will not be allocated unless there are any indexes to use ti.

No, your problem is probably OS related instead.

Which OS are you running?
Not a 64bit version i assume?

Either that or you have a ulimit set globally for how much memory each process are allowed to use.

On 32bit OS'es one process in itself can very rarely be allowed to allocate more than about 2-3GB due to limitations with using 32bit memory address space.

And on some Linux/BSD distributions they have a global ulimit that doesn't allow user processes to be larger than a certain size.
First check the ulimit limit with:

ulimit -a

If it says unlimited then it is not a ulimit problem and then unfortunately you need to run a 64bit version of your OS to be able to use more memory (which I think you should anyway since you have a pretty hefty server with a lot of RAM available).

And when you upgrade your OS to a 64 bit version you should also make sure that you are running a 64 bit version of MySQL