Jump to content

graysky

Members
  • Content count

    104
  • Joined

  • Last visited

Everything posted by graysky

  1. I read Verran's Guide on overclocking basics of Core 2 Duo chips but wanted to post my own guide. He did a great job, but mine is sort of a different flavor of chocolate. Have a read and see if you find it helpful. Edited on 08-Jun-2008: Guide is now version 1.7
  2. Edited on 08-Jun-2008: Guide is now version 1.7
  3. graysky

    lapped my Q6600 (pics and results)

    Sounds like you were met with great success! Glad to read it.
  4. Well, after lapping my HS, I've had this nagging little voice in my head telling me to do the same from the CPU. I did the job with 800 grit sandpaper. Initially, I told myself I'd just buff what's there right now just to see if it's level. After about 30 laps in one direction and 30 in the other direction I discovered I had quite a concave IHS. So I just kept at it. Two 9x11 pieces of 800 grit later paper later I was left with a darn flat layer of copper looking back at me. I finished the job and put a mild shine on it with a sheet of 1000 grit I got from the local auto parts store just for the crap of it. Here are a few pics and the temp. results I got from lapping both my CPU and HS. I would recommend that anyone wanting the best $20 decrease in temps should consider lapping both the CPU and HS. Hardware details: Q6600 @ 9x333 and vcore of 1.2625V in the BIOS, P5B Deluxe (vdroop modded) cooled w/ an Ultra-120 Extreme (lapped) with Scythe/s-flex SFF21F 1600RPM fan, in a P182 case: Temp results: Each temp. point represents an average of data collected over approx. 1 h time period during the 2nd pass of a 2-pass x264 encode of a 720x480 DVD source using a high quality video profile. Data points were logged by Speedfan every 3-4 seconds over this time period. The average CPU usage was >99 % on all 4 cores throughout the experiments. Also room temp was between 20-22
  5. Got bored yesterday, so I ran checked out the power consumption of my X3360 system for crap and giggles with my kill-a-watt. Powered Hardware Details: Intel X3360 (C1 stepping) @ 8.5x400=3.40 GHz 266/667 MHz Strap CPU Vcc=1.12500 NB Core=1.370 CPU VTT=1.310 DFI LT P35-TR2 (no modifications) eVGA 8800 GTSG92 512 meg (770/1,923/2,000 MHz : Core/Shader/Memory) Corsair Dominator DDR2-1066 (TWIN2X4096-8500C5DF) 2x 2Gb @ 5-5-5-15 (performance level 6) @ 1,000 MHz (4:5) @ 2.100V Corsair HX620 2x HDs (seagates, one a 10th generation and the other an 11th) 1x DVDROM 4x120 mm Tricool fans (came with the p182 case) all on low 1x120 mm S-Flex SFF21F (1600 RPM) on the HS 1x40 mm silent fan on the NB That's it... no other hardware (speakers, monitor, etc.) was in the loop. Kill-a-Watt Readings Idle in BIOS screens - 158 W Idle in BIOS screens with both HDD's unplugged - 144 W Idle (with speedstep active in XP x64) - 137 W Load (prime95 v25.6 small FFT) - 213 W Load (prime95 v25.6 large FFT) - 216 W Load (prime95 v25.6 blend) - 210 W Playing Crysis - 237-241 W x264 encode - 197 W Standby - 0 W No real point to this post beyond just trivial information! It is interesting to me that the large FFTs consistently read 3-4 watts higher than the small ones did which is inline with the software's description of the large FFTs as generating the max heat/power consumption. Here is the similar analysis of my older Q6600-based system, but there are too many changes (MB, settings, video board, memory, etc.) for a "which processor is more power efficient" comparison. What is little bit crazy is that both systems draw the same while idle, and even @ 3.4 GHz, and faster memory, the X3360-based system uses less wattage on p95.
  6. Yeah dude, look again at the first post (crysis).
  7. About 7 months ago I posted data comparing two memory dividers (1:1 and 3:5 @ 333 MHz) on my then Q6600/P965 based system and concluded that for the 67 % increase in memory bandwidth, the marginal gains in actual performance weren't worth the extra voltage/heat. Since then I've upgraded my hardware to an X3360/P35 setup and wanted to revisit this issue. Again, two dividers were looked at: one pair running 8.5x333=2.83 GHz, and another running @ 8.5x400=3.40 GHz: 333 MHz FSB: 1:1 a.k.a. PC2-5300 (667 MHz) 5:8 a.k.a. PC2-8500 (1,067 MHz) 400 MHz FSB: 1:1 a.k.a. PC2-6400 (800 MHz) 4:5 a.k.a. PC2-8000 (1,000 MHz) I figured there would be a much greater difference in the 333 FSB case since the memory bandwidth increased by 60 % vs. 25 % in the 400 MHz FSB case. All other BIOS settings were held constant with the exception of the divider (and the strap) and the given FSB. Subtimings were set to auto and as such could vary as managed by the board which I found out, was required since manually settings some of the subtimings lead to either an incomplete POST, or an unstable system. The benchmarks were broken down into three categories: 1) "Real-World" Applications 2) 3D Games 3) Synthetic Benchmarks The following "real-world" apps were chosen: x264, winrar, and the trial version of Photohop CS3. All were run on a freshly installed version of Windows XP Pro x64 SP2 w/ all relevant hotfixes. The 3D games were just Doom3 (an older game) and Crysis (a newer game). Finally, I threw in some synthetic benchmarks consisting of the Winrar self test, Super Pi-mod, and Everest's synthetic memory benchmark. Here is an explanation of the specifics: Trial of Photoshop CS3
  8. I edited the first post switching the highest 400 MHz FSB run from 5:6 to 4:5 (960 MHz vs. 1,000 MHz) and included some info about subtimings to make things more clear.
  9. Sorry dude, is there a question in there? You 10x multiplier isn't locked... if it's a q6700, it's 10x max, but you can dial it down to 6x if you want.
  10. Version 1.6.1 is up. Totally re-wrote the section on memory which now includes a discussion on both DDR2/DDR3 and formulas you can use to calculate max supported FSB of a given module based on it's DDRX-Y and PCX-Y designations. Also re-ordered the first part of the guide.
  11. Well, guys I wrote up this procedure I used to minimize my vcores on my new x3360/P35-based system, and I thought I'd share it with folks. It's a systematic method anyone can use to arrive at a minimized set of vcores for a given multiplier and FSB value. The examples I present in this post are using my X3360/P35-based system. The data aren
  12. OK, just got finished upgrading the guide to version 1.6!
  13. Can you provide us with some addition info? What multiplier and FSB? What are your vcores set to and what is your memory set to? What kind of memory do you have?
  14. I dunno about the P5N-SLI, but I would think it'd be fine. There is a short list of of recommended hardware types in the first few paragraphs of the guide. Once you get it put together you'll just have to try and see how far you can push it.
  15. Version is now 1.5.2 (updates in first post)
  16. Techarp is hosting a new HD x264 benchmark. Have a look and run it on your system to help populate the data table. Basically, you run the test encode of an HD sample (1280x720) and it will report back frames-per-second values for your machine @ it's clock/overclock level. You can run it at your stock settings and at your overclock settings to see how your machine compares to others in the database. My goal is to have a representative set of data for many different chips and chipsets. Please just report your results here in this thread. I will keep the data at that url to keep things simple. Thanks all and enjoy! The following image will be updated automatically as new data comes in. It doesn't display any results, but it does show the number of data points collected so far and how they break down by CPU type:
  17. Yeah, I did a SDTV version a while ago (here); this one uses an HDTV 720p clip since that's more or less the standard these days.
  18. 3 days later no takers?
  19. Wow dude, good catch... even though it was incorrectly typed out, my brain compensated for it as I read it Must be like this sort of effect. Fixed it, thanks!
  20. I don't understand what you're driving at here..??
  21. If you're running a 45 nm quad on an asus p5k (or any other P35 board for that matter), are you able to hit 8x400 or 8x450 okay? If so, what are your board voltages and mb temps (like north bridge temp or whatever readout that board displays for motherboard temps)? I ask because I'm thinking about getting a Q9450 next month on this board and since the multiplier is locked @ 8.0, I'll have to jack up the FSB. Thanks for the feedback all!
  22. graysky

    x264 video encoding benchmark

    First off, thanks to all who contributed data. 24-Feb-2008 - Finally updated the data tables on the x264 benchmark page. They are now html based (not .gif images) which makes my life updating them much easier and I will keep this tables up-to-date daily as people post results. Have a look at the 'Data Tends' table that contains a look at the Phenom quad vs. both Kentfield and Yorkfield quads. There are also some comparisons of Wolfdale dual vs. Conroe dual, and some other good stuff.
  23. I put together a self-contained x264 video encoding benchmark. Techarp kindly agreed to host the file and results at this URL. Basically, you run the test encode and it will report back frames-per-second values for your machine @ it's clock/overclock level. You can run it at your stock settings and at your overclock settings to see how your machine compares to others in the database. The database is small right now (as of 08-sep), but as you guys report in results, I will populate it. My goal is to have a representative set of data for many different chips and chipsets. Hopefully, we'll get some Penryn and Phenom data when they become available. Also, if anyone out here has some of the high end AMD chips, please contribute. Instructions and the file are at that url. Also, please report your results here in this thread. I will keep the data at that url to keep things simple. Thanks all.
×