top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is nPartition and Virtual Partition?

+1 vote
472 views

I am trying to understand nPar and vPar.

From this link I am getting very confused.

What is the meaning of partitioning hardware and software?

I have read somewhere that each nPar will run its own OS.(HP-UX). What is the meaning of that?

Can anybody help?

posted Oct 20, 2015 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes
 
Best answer

In short npar is a physical separation of a single computer into multiple partitions where each one having separate hardware components i.e. cell boards, I/O, memory etc.

vPars are Virtual partitions with separate operating system instances on the same physical nPartition or server. In short you you may have two OS each one is catering to one partition but both the partition share the CPU power or memory and Virtual Partitions make sure to dynamically move CPU power or memory between vPars as per load requirements.

answer Oct 20, 2015 by Salil Agrawal
Thank you sir,
Sir, Can you please clarify below things?
Basically Virtual partition is nothing but running Linux on Windows using VmWare or any virtual machine software. Right?
And sir, What about N-Partition, Can we have more than different OS running for different N-Partition?

Thanks in advance
Ideally yes, n-partition should allow you to run multiple OS with different partitions.
Thanks sir,

Sir, Virtual partition is under-stable, but for n-Partition i am still confused.

For example i have 2 n-partition. both have its own CPU/Memory/OS then why do we consider both as n-Partition why not Different System?
Similar Questions
+2 votes

I have read somewhere workload is nothing but a group of processes running under same compartment. Where compartment is n- Partition / virtual partition.

Is it correct?

+3 votes

I am using gprof on an HP-UX system for a program compiled with HP's native aCC (using the -G option, which is documented as compatible with gprof).

I get this every time I run gprof on even a small sample gmon.out:

$ gprof  gmon.out > gprof.out    
gprof: out of memory allocating ********** bytes after a total of 15552512 bytes

This works on other HPs we have in house, though I don't have access to them to be able to track down why.

Any clues that might point me in the right direction?

4,294,967,256 seems like an awful lot of memory to handle a 8,647,174 byte gmon.out file....

+3 votes

also please explain Virtual Memory Can Slow Down Performance why and how?

...