[SERVER-15990] Only issue NUMA and hugepages warnings for mmapv1 Created: 06/Nov/14  Updated: 21/Nov/15  Resolved: 21/Nov/15

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Andrew Morrow (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: polish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

The startup warnings relating to NUMA and hugepages configuration are specific to the mmapv1 storage engine. We should not issue them if we are using a storage engine other than mmapv1.



 Comments   
Comment by Charlie Page [ 06/Nov/14 ]

I'd have to see testing, but I imagine microsharding along NUMA for heap would be hugely beneficial. We 8 node boxes available for testing once we get stabilized.

However, it is possible that storage engines are NUMA aware, so making this per storage engine is a good idea. I'm just not aware of any that like NUMA/THP.

Comment by Andrew Morrow (Inactive) [ 06/Nov/14 ]

I guess my point is more accurately stated that these startup warnings should be per-storage-engine, not global. Surely the heap storage engine does not care?

Comment by Charlie Page [ 06/Nov/14 ]

http://source.wiredtiger.com/develop/tuning.html

Wired tiger seems to disagree that these aren't important. Is there some WT notification?

Generated at Thu Feb 08 03:39:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.