Differences between revisions 6 and 7
Revision 6 as of 2016-03-21 06:18:35
Size: 941
Editor: ?dbp
Comment:
Revision 7 as of 2016-08-12 03:34:12
Size: 933
Editor: ?dbp
Comment: Fixed ambiguous terms
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
There is confusion for using the term "Host" to represent "Guest". To let reader clear, it is suggested to make the terms consistent: The terms "Host", "Server", "Client", "Guest" and others may be ambiguous to readers. Below is current practice:
Line 7: Line 7:
1. A system running on physical resources is called "Host" / "Server". 1. A system running on physical resources is called "Host".
Line 9: Line 9:
2. A system running on resources provided by "Host" / "Server" is a "Guest" / "Client". 2. A system running on resources provided by "Host" is called "Guest".

3. Avoid using
"Server" and "Client".

Describe KVM/Discussion here.

Terminology

The terms "Host", "Server", "Client", "Guest" and others may be ambiguous to readers. Below is current practice:

1. A system running on physical resources is called "Host".

2. A system running on resources provided by "Host" is called "Guest".

3. Avoid using "Server" and "Client".

Huge Page Support

For Huge Page support, the only use case found was with Oracle Database which reduced the Page Table size from 5GB to 200MB and suppressed memory swapping. In actual use, my VM server with 13 VM clients (with 1 Windows VM client running Oracle Database and the rest Windows / Debian VM clients without Oracle Database running) with only 100MB page table size in VM server. Under this situation, CPU / memory benchmarking with Huge Page support enabled shows no performance gain (benchmark deviation is larger than the benchmark results differences).