Home › Blogs › kkawahara's blog

Luminis IV Memory Configuration

Tue, 2008-07-01 15:42 — kkawahara
4
Average: 4 (1 vote)

Back at summit, people who have been through an upgrade to IV reported seeing memory utilization on either their DB or resource box go way up (opposite in fact from what they saw in III), but I can't remember if it was III uses more DB memory, or IV uses more DB memory.

We're building a new environment (windows), and if we need more than 4 GB on either box, we need to use Win2003 Enterprise, since standard only goes up to 4GB.

Anyone remember what the pattern was?

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Tue, 2008-07-01 16:10 — rbalara

Sorry I don't have any

Sorry I don't have any answer to your exact question, but the 4 GB limit isn't a licensing issue in your case. The 4 GB limit is a limit of the 32-bit memory architecture. If you get the 64-bit verison of Windows Server 2003 Standard, the limit is 32 GB. I would check to confirm that 64-bit Server 2003 is supported, but if it is, there shouldn't be a problem.

Edit: The memory limitations are noted here: http://msdn.microsoft.com/en-us/library/aa366778.aspx

Tue, 2008-07-01 16:51 — kkawahara

not for server

Thanks for the table. If you check the listing for Server 2003 though, you'll see that Enterprise and Datacenter editions can go past the 4 GB limit even with 32 bit windows. I believe it uses the same extended paging that linux uses (so per proc memory usage is still capped).

Wed, 2008-07-02 12:20 — rbalara

Absolutely! I didn't mean to

Absolutely! I didn't mean to imply otherwise. That's why I suggested 64-bit Server 2003 standard, if that's possible, since it doesn't have the same per processor limitations. Anyway, I hope my info helped.

Thu, 2008-07-03 06:02 — kkawahara

I'm a bit confused by your

I'm a bit confused by your response, since your initial message said "The 4 GB limit is a limit of the 32-bit memory architecture", but the table does show 32 bit windows can use more than 4 GB if you use Enterprise Edition or Datacenter Edition (32 bit flavors) - it is a licensing issue. Also, when I said per proc - I meant per process, not processor.

In any case, we just went with Enterprise Edition (32 bit) so we can add ram if necessary.

Thanks for the info again.

Thu, 2008-07-03 12:09 — rbalara

Alright, that works. Sorry

Alright, that works. Sorry to confuse you. The 32-bit memory limitation is still not a licensing issue, but, according to my readings, the datacenter and enterprise editions overcome this via PAE. This explains why the standard edition has a lower maximum memory limitation. If it were truly a licensing issue, then the 64-bit version of the same OS would have the same limitation unless MS went crazy with their licensing methods (wouldn't be the first or last time).

Nice catch on the memory limit per process...you are correct on that. I typed processor but meant process.

Good luck with your new environment!

-Ryan

Thu, 2008-07-03 14:08 — Jason

db bottleneck

Going from III.3.3 to IV, we saw a very large increase in CPU and memory use on the database server. Our resource/ldap server was about the same.

Our prior 333 system was on HPUX. Our new IV system is on Solaris 10. Our DB is oracle.

We started out with 2cpu/16gig ram for our DB, and 4xCPU/16gig ram for our resource tier. After our first registration showed the DB being worked much harder than the resource tier, we swapped the boxes, and now the DB has the 4cpu and 16gig ram.

Not sure what your load is going to look like, but I mention in my blog a couple indexes that can be added to improve DB performance if you do find that it is an issue.

Wed, 2008-07-09 04:51 — kkawahara

THANKS!

exactly the story I was looking for. thanks.