Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Best performance UNIX just for HOST Virtualization? Post 303012319 by bakunin on Friday 2nd of February 2018 05:34:27 AM
Old 02-02-2018
One big distinction you might want to make when it comes to virtualisation is "para-virtualisation" versus "full-virtualisation".

The difference is that a para-virtualised system is aware that it is virtual. This means that it can forego some tasks a non-virtualised system would have to do:

i.e. a disk driver needs to check if the disk is still accessible, may have to cover for a block becoming bad, etc.. A fully virtualised disk driver thinks that the (virtual) disk it is presented is in fact a real disk and treats it accordingly. It will do all these checks i talked before. A para-virtualised disk driver would "know" that what seems to be a disk is in fact a file on some real disk and forego all these checks because the disk driver of the host system would carry them out anyway. This will make the para-virtualised driver faster and less resource-consuming. On the other hand it would mean that you have a system with a different driver and you can't simply copy your physical system to a virtual environment (or the other direction) without changing some things.

I haven't worked with OpenVZ for a long time, so i cannot say anything about newer versions. OpenVZ is (was?) such a para-virtualised environment which offers performance benefits compared to fully virtualised environments like VirtualBox, etc.. But basically it is (or was?) a very comfortable chroot-environment and the performance gain meant on the other hand, that you had only one kernel really running. This meant that you were not completely independent in chosing the system you wanted to run virtualised. If it is now possible to mix Windows- and Linux-systems on the same hardware node IMHO this means that they have switched to full virtualisation and this perhaps means giving up some/all of the performance advantages the para-virtualised system once had.

But without more clearly defining what you want to do a serious suggestion is not possible, as already has been said times and again.

I hope this helps.

bakunin
 

4 More Discussions You Might Find Interesting

1. Solaris

ILOM to unix host

Hello- On Solaris 10g x86 - I had two IP addresses , one for unix host (connecting through putty) and one for ILOM (connecting through CLI and web). I had to perform some changes in FS sizes etc, did that on unix host and executed command 'init 6' remotely for them to take place. But, the unix host... (30 Replies)
Discussion started by: panchpan
30 Replies

2. Red Hat

Red Hat and Intel: Smart processors, virtualization boost efficiency and performance

On Monday March 30, Intel announced the availability of their much anticipated new line of processors, the Intel® Xeon® Processor 5500 series–nicknamed Nehalem. Red Hat, a long-time partner of the market-leading chip maker , collaborated on the chip’s debut, testing and optimizing the... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. UNIX for Dummies Questions & Answers

Virtualization of Global Namespace in UNIX

Hi all, I have a small Question here in Unix File System.I am unable to get a proper answer in Internet. Hope someone can get back to me soon. A Unix file system can mount filesystem of several disk partitions to form a single global space. Suppose that you wish to virtualize this global... (1 Reply)
Discussion started by: Pavan Kumar
1 Replies

4. Red Hat

Virt-install: ERROR Host does not support any virtualization

Hello guys! First of all sorry about my english. I am using KVM to virtualizate. But when i run the virt-install command, it shows the next error: ERROR Host does not support any virtualization options.My server had virtualisation extensions enabled in the bios. It is my first time using... (7 Replies)
Discussion started by: morrison71
7 Replies
max_async_ports(5)						File Formats Manual						max_async_ports(5)

NAME
max_async_ports - maximum number of asynchronous disk ports that can be open at any time VALUES
Failsafe Default Allowed values Recommended values There is no recommended value for this tunable. The number of processes that will be accessing the driver simultaneously can be used as a guideline to set a value. DESCRIPTION
The asynchronous disk driver provides an interface to execute high-performance I/O to the raw disk. Instead of reading or writing directly to the raw disk, a process writes requests to the asynchronous driver which then makes appropriate calls to the disk driver. Every process that opens the asynchronous disk driver is assigned a port. The driver uses the port to keep track of I/O and other internal resources for that process. The number of opens to the asynchronous disk driver is limited by the number of available ports. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately if the new value is allowed; otherwise the change takes effect at next boot. Increases within the allowed range are always accepted immediately. Decreases in the value may take effect immediately, or may be deferred until next boot depending on the current number of ports in use or the maximum number of ports ever used. When Should the Value of This Tunable Be Raised? When the number of processes opening the driver needs to be more than the current value of the tunable. What Are the Side Effects of Raising the Value of This Tunable? The resources for the port are allocated from the kernel memory. Setting a higher value would result in the driver using slightly more kernel memory. Other kernel components which may need kernel memory could suffer. However, the amount of memory reserved for each port is low. Only when a new port is actually issued does any significant amount of memory get consumed. When Should the Value of This Tunable Be Lowered? There should be no real need to lower the value of the tunable. However, if many processes are opening the async driver and allocating ports, then lowering the value will put a cap on the maximum number of ports that can be allocated and will put a cap on the maximum amount of memory that the driver may allocate. What Are the Side Effects of Lowering the Value of This Tunable? The number of simultaneous opens are limited by this tunable. This may impact the performance of applications that need to have a higher number of processes accessing the driver. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. Tunable Kernel Parameters max_async_ports(5)
All times are GMT -4. The time now is 10:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy