I am trying to set a larger buffer size in my NIC card. I am following the instruction provide by Intel , but i think it didn't made any changes. Please see the image:
on 01/03/2013 – Made popular on 01/03/2013
You need buffer pool a bit (say 10%) larger than your data (total size
of Innodb TableSpaces)
On the other hand I've read elswher that innodb_buffer_pool_size must be up to %80 of the memory. So I'm really confused how should I choose the best size for the pool. My database size is about 6GB and my total memory 64GB.
fukawi2 wrote:Now these defects are in 'stable' kernels (Debian, RedHat etc) too but there is a much larger buffer time-wise for them to be discovered and rectified between Linus releasing a given version and that same version being released as a stable Debian/RedHat etc kernel compared to when Arch will release it.That is why I'm thinking of Debian as the (inexpensive) alternative.
We have a redhat 6 servers and memory is around 64GB, we are planing to configure kdump and I am confused about disk size I should set. Redhat suggest it would be memory + 2% more. I need your suggestion what would be the best size I should define for kdump
I am using Parcelable classes to pass data between Activities. As the documentation suggests, I keep all transactions relatively small (100kb) because the Binder transaction buffer has 1Mb capacity. The problem is that if I repeat a small transaction many times the buffer reach that size and the os throws android.os.TransactionTooLargeException.