This implemented differently in MDEV-10814 (10.3.7+) as an always on function.
Could look at attempting a core_pattern (man 5 core) script that filters out aspects though I don't know how to do that. A gdb script maybe.
coredump_filter doesn't seem usable, unless with huge pages which is horrible and getting fixed in 10.5 (MDEV-18851).
Thank you Daniel! Some thoughts
- Ack on
MDEV-10814! - Some further research shows that cores generated are 1.2GB in size on 128GB server, so seems reasonable as-is.
- Looking at man 5 core, coredump_filter may work also to reduce further (and gdb script would not work as that is post-core-generation)
In summary, I will close this request for the moment. Thank you.
I had a 10.1/10.2 thought for you. In your test environment after the server is started, execute a gdb script with `call madvise(
{approprate buffer pointer},size, MADV_DONTDUMP);`
It has to be done with every chunk of the innodb buffer pool, so reducing the number of pools and increasing the chunk size will result in less calls.
buf_pool_ptr[i] and then to chunk:
how allocated: https://github.com/MariaDB/server/blob/mariadb-10.2.22/storage/innobase/buf/buf0buf.cc#L1533
or take addresses/sizes out of /proc/$(pidof mysqld)/smaps
ref: call https://sourceware.org/gdb/onlinedocs/gdb/Calling.html
ps. glad MDEV-10814 is working so well you didn't even notice 
Yes And thank you for the 10.1/10.2 tip!