1854662 Members
8443 Online
104102 Solutions
New Discussion

Re: ipcs vs TCP/IP

 
Gavin Clarke
Trusted Contributor

ipcs vs TCP/IP

This may not be the right place, however here goes:

I'm looking for information about how to compare the speed of ipcs vs. TCP/IP, I know one is a databasey thing and one is a network protocol, still.

Reason is that we have two L Class servers in a serviceguard cluster running HPUX 11.0. These are running J D Edwards with an Oracle database. There are two ways of configuring this, one the JD Edwards bit is on the opposite server to Oracle, the other they're both together.

The advantage of both together is that JD Edwards can then use ipcs to talk to Oracle, how much of an advantage is this?

PS: We have Gigabit connections between servers.

Any documents or useful info gratefully received.
4 REPLIES 4
Stefan Farrelly
Honored Contributor

Re: ipcs vs TCP/IP

Well, in my opinion ipcs (inter process communication) is going to be a fair bit faster than using TCP - even over Gigabit.

But more importantly - will Oracle and JD Edwards co-exist together ? They could interfere with each other - affecting each others performance. For example, Oracle is cpu intensive - if someone kicks of some large reports they will hammer all available cpus - and JD Edwards may suffer considerably as a result. You need to investigate and test these things. For that reason it may be better to split them on different servers.
Im from Palmerston North, New Zealand, but somehow ended up in London...
Gavin Clarke
Trusted Contributor

Re: ipcs vs TCP/IP

Thanks for the reply, yes our dba mentioned a similar argument, his was memory related.

Really I can't think why we would want to change the configuration we've got now, I suspect it won't be under pressure. Still I was hoping to find some documents that could maybe give me some clues as to which is best.

I don't find JD Edwards Knowledge Garden particularly easy to use.
Tim Sanko
Trusted Contributor

Re: ipcs vs TCP/IP

I have experience with JDE since it was on the IBM system 34, which accounts for much of my grey hair.

IPCS is much faster. Depending upon user load, it may make sense to place the DB and app on separate servers, personally I'd put them on the same server first. That allows for ipcs and beq type connections to the database. Much faster than a sqlnet connection.

However if the J class boxes are old J2000s with 2 400MZ CPUs, there may be no real visible improvement no matter how you configure things.

Tim
Gavin Clarke
Trusted Contributor

Re: ipcs vs TCP/IP

I think I might be thinning a bit at the front.

I'm sure I said L Class though.

Thanks Tim for the reply, it's reassuring to know others are out there having the same problems.