 |
 |
> On Feb 18, 2016, at 1:20 PM, Van Klaveren, Brian N. <[log in to unmask]> wrote: > > You could probably fill the pages in at 85% or more. > > https://mariadb.com/kb/en/mariadb/xtradbinnodb-server-system-variables/#innodb_page_size <https://mariadb.com/kb/en/mariadb/xtradbinnodb-server-system-variables/#innodb_page_size> That link doesn’t seem to be related to fill factor. I was looking for something like this http://dev.mysql.com/doc/refman/5.7/en/index-page-merge-threshold.html <http://dev.mysql.com/doc/refman/5.7/en/index-page-merge-threshold.html> in Maria, but cannot find it. That link says that the page merge threshold used to be hardcoded at 50% free, hence my worst case estimate. It’s plausible that this is way too pessimistic in practice, and that sorting before loading results in relatively full pages. I just don’t know for certain. > I can't tell how much you can modify the percent free per block/page though. > > I'm not sure if this is applicable either: > https://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-row-format-dynamic.html <https://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-row-format-dynamic.html> I don’t think so - that seems to be about storing long column values in overflow pages, and we don’t have any of those here. Serge ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1