percona-discussion team mailing list archive

[Yasufumi Kinoshita <yasufumi.kinoshita@xxxxxxxxxxx>]

It may be InnoDB-Plugin's bug.

Did you test 16G, 12G, 8G, 4G also?
And did 19G work fine? (Did 19G really allocated? Was it 3G?)

"InnoDB: VirtualAlloc(0 bytes) failed; Windows error 87",
"0 bytes" means size == 0 at
os/os0proc.c: 132
	size = *n = ut_2pow_round(*n + (system_info.dwPageSize - 1),
				  system_info.dwPageSize);

I don't have Windows-64bit env. So the following is just a estimation.

I suspect system_info.dwPageSize may be 32bit in Windows.
If so, we may need to change it to
	size = *n = ut_2pow_round(*n + ((ulint)system_info.dwPageSize - 1),
				  (ulint)system_info.dwPageSize);

Sorry, I cannot confirm it for now.

-- 
XtraDB don't start if innodb_buffer_pool_size>19G
https://bugs.launchpad.net/bugs/330109
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraDB.

Status in Percona XtraDB Storage Engine for MySQL: New

Bug description:
On Intel server (24 core, 48Gb) under Win 2008 I have error when set innodb_buffer_pool_size=20G:
InnoDB: VirtualAlloc(0 bytes) failed; Windows error 87
InnoDB: Fatal error: cannot allocate the memory for the buffer pool

In "std" InnoDB all work fine with  innodb_buffer_pool_size>19G.