01-18-2016
NX 3 had a dump round-robin dispatcher. If one of the NX nodes was rebooted, it was less loaded than the other nodes, and never caught up.
The nxpub simply adds a more sophisticated dispatcher, and is transparent i.e. there is no administrative change and no extra dependency.
If you are using another load balancer, then likely this one won't add any value.
5 More Discussions You Might Find Interesting
1. Programming
Halo mates,
I m going to write a load balancer with C. Does anybody know some good reference on this?
Cheers,
Elton (5 Replies)
Discussion started by: EltonSky
5 Replies
2. AIX
Hi All,
How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive).
Any idea, please.
Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies
3. Red Hat
Hi,
What's the best load balancer for Linux (CentOS, SuSE) according to your personal experience?
Linux Virtual Server (LVS) is a famous one, but their download site has not been updated since 2007. Their web and mailing list are so quiet. Is the Ultra Monkey project including LVS... (1 Reply)
Discussion started by: aixlover
1 Replies
4. UNIX for Advanced & Expert Users
we use piranha load balancer with two nodes
even the primary node is running fine and up failover happend to secondary node
this happend quite few times ehy node2 cannot talk to node1
what logs are to be checked and investigate why failover occured
pulse: partner dead: activating... (0 Replies)
Discussion started by: robo
0 Replies
5. Linux
Hello Guys,
Hope you all doing well . :)
I was checking load balance command (uptime)on VM server and got below output.
# uptime
07:08:40 up 52 min, 2 users,a load average: 0.45, 0.11, 0.03
A :How we can calculate load average?
Thank you in advance !!
Cheers:)
Dont forget... (1 Reply)
Discussion started by: Nats
1 Replies
LEARN ABOUT LINUX
migratepages
MIGRATEPAGES(8) Linux Administrator's Manual MIGRATEPAGES(8)
NAME
migratepages - Migrate the physical location a processes pages
SYNOPSIS
migratepages pid from-nodes to-nodes
DESCRIPTION
migratepages moves the physical location of a processes pages without any changes of the virtual address space of the process. Moving the
pages allows one to change the distances of a process to its memory. Performance may be optimized by moving a processes pages to the node
where it is executing.
If multiple nodes are specified for from-nodes or to-nodes then an attempt is made to preserve the relative location of each page in each
nodeset.
For example if we move from nodes 2-5 to 7,9,12-13 then the preferred mode of operation is to move pages from 2->7, 3->9, 4->12 and 5->13.
However, this is only posssible if enough memory is available.
Valid node specifiers
all All nodes
number Node number
number1{,number2} Node number1 and Node number2
number1-number2 Nodes from number1 to number2
! nodes Invert selection of the following specification.
NOTES
Requires an NUMA policy aware kernel with support for page migration (linux 2.6.16 and later).
migratepages will only move pages that are not shared with other processes if called by a user without administrative priviledges (but with
the right to modify the process).
migratepages will move all pages if invoked from root (or a user with administrative priviledges).
FILES
/proc/<pid>/numa_maps for information about the NUMA memory use of a process.
COPYRIGHT
Copyright 2005-2006 Christoph Lameter, Silicon Graphics, Inc. migratepages is under the GNU General Public License, v.2
SEE ALSO
numactl(8) , set_mempolicy(2) , get_mempolicy(2) , mbind(2) , sched_setaffinity(2) , sched_getaffinity(2) , proc(5) , ftok(3) , shmat(2) ,
taskset(1)
SGI Jan 2005 MIGRATEPAGES(8)