Ram bottleneck? - testmy.net resource / tool
Home
Welcome, Guest. Please login or register.
Did you miss your activation email?

 



donations help testmy.net pay for the very high cost to run the site. Any amount is greatly appreciated.
Click to read why...

  spcr
    
News : undecided Is blue NOT your favorite color?  Well why not customize testmy.net to your liking?!  We offer over 25 theme variations, there is sure to be at least one that suits your personal style, choose one here cool October 07, 2008, 02:19:35 AM
testmy.net Broadband  |  Main Forum  |  HELP!  |  Overclocking  |  Topic: Ram bottleneck? Advanced search
  0 Members and 2 Guests are viewing this topic. « previous next »
Pages 1 Go Down
Author
Topic: Ram bottleneck?  (Read 792 times)
Le_Murphant
TMN Friend
*
Offline Offline

Gender: Male
Posts: 371



View Profile
« on: January 29, 2008, 09:21:49 PM »

I recently decided overclock my e6600 and I was able to put it to 350FSB with 9x multiplier quite easily. I probably would have been able to push it farther but I was wondering if my ddr2-667 ram, clocked at 700MHz, would bottleneck it since its real clock speed is 350MHz and I can't seem to push it farther than that. Would I see an improvement if I put my cpu fsb at say 400 even though my ram was at 350? I plan on upgrading my ram eventually, but probably not for 6 months or so; I'm hoping the advent of ddr3 can make prices for high-end (500fsb+) ddr2 drop.

I am also wondering about what "read" and "writes" such as seen in process explorer really are. Are they read and writes to the cpu cache, the ram, the hard drive or any of the above? And how is the limit affected by fsb?
Logged
Print  Pages 1 Go Up
testmy.net Broadband  |  Main Forum  |  HELP!  |  Overclocking  |  Topic: Ram bottleneck? « previous next »
Jump to:  

    
testmy.net's forum is proudly Powered by SMF | SMF © 2006-2007, Simple Machines LLC
Bookmark: Del.icio.us    StumbleUpon
 
 

 

© 1999-2008 testmy.net - Contact - Legal - Facts & FAQs
Page Loading Stats: This forum Page created in 0.081 seconds with 25 queries.