07-16-2013
Diameter protocol performance on RH 6.4
Hi,
I recently upgraded from RH 6.2 to RH 6.4 on our diameter application server. After the upgrade, we saw the performance throughput of out diameter application went down about 40%. From 459K transaction per second to 234K TPS on RH 6.4. Nothing has changed in the network. I am using HP G8 with 24 cpus. Does anyone have any idea of what could cause this? and how to get around it.
Thanks,
Ketan
9 More Discussions You Might Find Interesting
1. IP Networking
I have a small program written in C using winsock v1, that uses a unix host to get the time.
I have two machines networked, one windows, the other red hat 9.
The windows machine will request the time off the RH one.
How can I configure red hat to reply to the time request, i.e act as an... (1 Reply)
Discussion started by: jaredGalen
1 Replies
2. IP Networking
I'm planning on putting together a chart of basic information (port number, protocol number, transport layer protocol, etc) on different protocols (FTP, ICMP, DNS, IP, etc)
I found:
http://www.phys-iasi.ro/Library/RFCs/rfc1700.htm
and that tells me a little bit of information but I'm looking... (3 Replies)
Discussion started by: thmnetwork
3 Replies
3. IP Networking
iam doing a research on WAN so pliz any body can give me or tell me where i would find communication protocol map..thats all 7 layers..OIS MODEL (1 Reply)
Discussion started by: ravineelkumar
1 Replies
4. UNIX for Dummies Questions & Answers
To check the protocol level, we need to change its
entry in sshd_config. Below are my 2 servers with
OpenSSH as 3.7.1. I have changed its protocol to 1 and
reboot the box and below is the output
sysp02adm@sysp02 # telnet localhost 22
Trying 127.0.0.1...
Connected to localhost.
Escape... (0 Replies)
Discussion started by: yls177
0 Replies
5. UNIX for Advanced & Expert Users
Is there any way to access http page from UNIX command line....
eg: http://www.abc.xyz (5 Replies)
Discussion started by: bishweshwar
5 Replies
6. News, Links, Events and Announcements
About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies
7. Infrastructure Monitoring
dear friends ,
how can I use the SNMP protocol to monitor the network and send notification alerts to the clients which have windows machines.
I found the utility snmp_trapsend at the directory /usr/sbin ,how can I use this command ??
my server is SUN SOLARIS.
please help !!!:confused: (1 Reply)
Discussion started by: Ahmed waheed
1 Replies
8. IP Networking
actual transmission path is physical layer. do peers in n layer communicate on any issue using n layer protocol with each other. as far as i know this communication is said to be virtual. (0 Replies)
Discussion started by: zius_oram
0 Replies
9. IP Networking
Hello Forum Members,
I am siva ranganath from Hyderabad-India.
I have an work experince of 4.5 years as application developer and support member in open source systems.i am good basic network programing ie applications developing in TCP/IP and i have an experince of 1 year in this N/W... (0 Replies)
Discussion started by: workforsiva
0 Replies
relup(5) Files relup(5)
NAME
relup - Release upgrade file
DESCRIPTION
The release upgrade file describes how a release is upgraded in a running system.
This file is automatically generated by systools:make_relup/3,4 , using a release resource file ( .rel ), application resource files ( .app
) and application upgrade files ( .appup ) as input.
FILE SYNTAX
In a target system, the release upgrade file should be located in the OTP_ROOT/erts-EVsn/Vsn directory.
The relup file contains one single Erlang term, which defines the instructions used to upgrade the release. The file has the following syn-
tax:
{Vsn,
[{UpFromVsn, Descr, Instructions}, ...],
[{DownToVsn, Descr, Instructions}, ...]}.
* Vsn = string() is the current version of the release.
* UpFromVsn = string() is an earlier version of the release to upgrade from.
* Descr = term() is a user defined parameter passed from the systools:make_relup/3,4 function. It will be used in the return value of
release_handler:install_release/1,2 .
* Instructions is a list of low-level release upgrade instructions, see appup(5) .
It consists of the release upgrade instructions from the respective application upgrade files (high-level instructions are translated
to low-level instructions), in the same order as in the start script.
* DownToVsn = string() is an earlier version of the release to downgrade to.
When upgrading from UpFromVsn with release_handler:install_release/1,2 , there does not have to be an exact match of versions, but
UpFromVsn can be a sub-string of the current release version.
SEE ALSO
app(5), appup(5), rel(5), release_handler(3erl), systools(3erl)
Ericsson AB sasl 2.1.9.3 relup(5)