Is an upgrade of the memory on a SNAP 2000 a worthwhile exercise?

[MaddMatt]

Snap 2000 Memory Upgrade system Snap Server 2000 OS: 4.0.860 HW 2.0.0 BIOS 2.0.252 HDD's 2x80GB

I have a Snap 2000 20GB 2x 80GB HDD’s, that has issues when I do big transfers to it, I am checking on the possibility of the CPU fan being faulty but;

One poster noted on a 4000 that big transfers can have issues and a memory upgrade would help on the 4000 (it may only help with RAID 5);
Question about the Snap 4000
http://forums.procooling.com/vbb/showthread.php?t=13929
Under this thread even though it is about a SNAP 4000 one of the guys says;
“If you use larger drives, you will most likely need to upgrade the memory to 128 MB if it's not already, especially if you load JVM. If you don't, when you try to transfer large amounts of continuous flow data (large files), you will get errors and the transfers can/will fail.”

Another poster intimated that a memory upgrade on a 2000 is not worth it;
Comparing transfer rates with different RAM amounts
http://forums.procooling.com/vbb/sho...ap+server+2000
This thread has 57 replies, it starts of with a Snap 2000 but ends up discussing a Snap 4000 but in the middle it intimates that it really is not worth upgrading the RAM on a Snap 2000 because the SNAP Operating System does not know how to use the extra RAM?

Is an upgrade of the memory on a SNAP 2000 a worthwhile exercise?

[blue68f100]

If you are or have JVM loaded, definately upgrated the ram to 128. It take a low density DIMM's. Most people have old ram laying around. If you are handling large files it will not hurt. If the transfer is a bunch of small files proably not.

Now with that said, there are several factors that effect file transfers. Number of users, size and number of files. The FAQ's show the max file size a snap can handle. It's also posiable you may be loosing packets or having packet collisions. Even routers or switches them self can over heat during heavy traffic. Try a direct connect with a crossover cable and see it the problem clears.

[MaddMatt]

I am not running JVM but as long as it is worthwhile I'll upgrade it to see if it helps the transfers;

Is there a special process for upgrading the memory and once installed do you have to run any debug commends to make the OS recognize it?
Also; How do you determine if your memory is Low Density?

Thanks in advance!

Matt

[Phoenix32]

It was me who said you needed 128MB memory for large file transfers on larger drive units. I do not know where the cutoff is for what is large an what is not, but with 4 x 250 GB in RAID 5 on the 4000, it is needed. Now without the RAID 5, I don't know, I did not test that. And will it make a difference that it is only 2 drives instead of 4? I don't know that either. Sorry, but I did not test my 4000's with only 2 drives and other than for the speed tests, I set my units up to RAID 5.

[MaddMatt]

Thank you for the feedback, once I work out how to upgrade the RAM and how to tell what Low Density RAM is I will definitely leave the feedback on this post.

I will test it (like it is) to make sure I can replicate it (and check if the fan works at all…) then I will try it with more RAM to see if it stops the 2000 dropping of the network.

Please kindly let me know if there is anyone out there who has had a similar problem that was solved by a RAM upgrade

[blue68f100]

Once you replaced the ram chip, run "debug memory" from debug. It will tell you how much it reconized. If you are only seeing 1/2 its high density. On the larger densitys the ram must be on both sides of the chip. This is how we tell for 256, don't know on the 128megs.

[Phoenix32]

You are very welcome, I hope it works out for you...

As for low density ram, it has to do with how the matrix/cells are set up. Honestly, it is way more than I want to type up at the moment for a detailed explaination. But as David said, for a 256MB, if the RAM chips are on both sides of the stick, there is a good change it is not high density memory, but not for 100% sure. For 128MB, 64MB, or 32MB, it can go either way (single or double sided).

If you read the specs on the manufacturers web sites, you can usually find the information. If not, look to see their compatibility lists. If it is showing that memory you are looking at as NOT compatible with P2 and older P3 systems, then it is high density, and not what you want.

Also, some places (like newegg) have customer reviews for the products on their web sites. Quite often, if you read those reviews, someone will say it is high density or not.

And if all that don't work for you, there were some message threads here on the forum somewhere that various people have posted what memory (make and part number) worked for them. One caveat to this is, SOME manufacturers change their memory over time from one type to another, but retain the same part number. There just is no way to know for 100% sure unless you look at the specs of the RAM and know what you are looking for and how and what chips are being used.

Yeah, I know it was not a ton of help, but it will get you started. Hope this corrects your problem for you.

[MaddMatt]

Hey Guys,

I installed a stick of 128MB and ran the command

* (I take it by thsi figure that this means that the 128MB stick is Low Density
are the rest of the readings ok?

Also while I was running this command the fan started and it sounded like a giant bloody bumble bee! - so it is fubar'ed and needs replacing...

03/06/2007 20:49:51 Command: debug memory

Total System Physical Memory: *134217728
File System Memory Allocated: 118680768
Memory To be Written: 0
Memory On Loan: 0
Loan Count: 0
Heap Memory: 109032928
Memory In Use: 107393328
Objects Allocated: 23
Communication Memory Allocated: 1758688
Memory In Use: 465176
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 15964
Handles Allocated:4679
Handles In Use: 354
SDB Volatile Memory Allocated: 98304
Memory In Use: 304
Handles Allocated: 11705
Handles In Use: 11
System has been configured!

------------
Command executed without error.

[MaddMatt]

Here is a 256MB

03/06/2007 21:03:11 Command: debug memory

Total System Physical Memory: 268435456
File System Memory Allocated: 248746320
Memory To be Written: 124560
Memory On Loan: 0
Loan Count: 0
Heap Memory: 229134752
Memory In Use: 226344736
Objects Allocated: 23
Communication Memory Allocated: 2059232
Memory In Use: 466040
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 15964
Handles Allocated:4679
Handles In Use: 354
SDB Volatile Memory Allocated: 98304
Memory In Use: 304
Handles Allocated: 11705
Handles In Use: 11
System has been configured!

------------
Command executed without error.

Here is a 64MB


03/06/2007 21:08:35 Command: debug memory

Total System Physical Memory: 67108864
File System Memory Allocated: 54324768
Memory To be Written: 0
Memory On Loan: 0
Loan Count: 0
Heap Memory: 49619600
Memory In Use: 48607248
Objects Allocated: 23
Communication Memory Allocated: 1524152
Memory In Use: 464344
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 15964
Handles Allocated:4679
Handles In Use: 354
SDB Volatile Memory Allocated: 98304
Memory In Use: 304
Handles Allocated: 11705
Handles In Use: 11
System has been configured!

------------
Command executed without error.

[Phoenix32]

Looks like you got the right memory sticks to me...