The AnandTech Podcast: Episode 10by Anand Lal Shimpi on November 21, 2012 12:40 AM EST
- Posted in
- Cloud Computing
We've made it to 10 episodes of the AnandTech Podcast! As promised, this week's episode is a bit more PC focused as we discuss the future of AMD. Intel's SSD DC S3700 is up for discussion, as well as the HPC space including the launch of Intel's Xeon Phi (baesd on the architecture formerly known as Larrabee).
There's a bit of mobile discussion in the second half of the podcast, addressing TI's exit from the market and some final thoughts on the Nexus 4 from Brian.
The AnandTech Podcast - Episode 10
featuring Anand Shimpi, Brian Klug, Ryan Smith & Dr. Ian Cutress
RSS - mp3, m4a
Direct Links - mp3, m4a
Total Time: 2 hours 3 minutes
Outline - hh:mm
Intel SSD DC S3700 and the Evolution of SSDs - 00:01
Intel's Xeon Phi - 00:16
AMD in the HPC Space - 00:41
AMD's Tough Times - 00:55
TI Exiting the Mobile SoC Business - 01:32
More on the Nexus 4 - 01:44
As always, comments are welcome and appreciated.
Post Your CommentPlease log in or sign up to comment.
View All Comments
dishayu - Wednesday, November 21, 2012 - linkIt always seems like a long wait between podcasts to me. Definitely the high point of my day when it comes out though. Looks like a good one from the outline. Listening to it now.
noblemo - Wednesday, November 21, 2012 - linkEnjoyed listening to all the topics in this edition of the podcast. Sounds like thermal throttling on the Nexus 4 isn't a deal breaker, especially if you buy into the greater philosophy of the device.
Have a great holiday.
LadyKate - Sunday, November 25, 2012 - linkLove my job, since I've been bringing in $5600… I sit at home, music playing while I work in front of my new iMac that I got now that I'm making it online(Click on menu Home)
IanCutress - Wednesday, November 21, 2012 - linkSince this podcast was recorded, I essentially spent all weekend playing around with C++ AMP. It definitely gets around my 'Don't want to program on AMD cards' issue :) Currently trying to make a benchmark with it involving grid solvers, but it all seems too CPU limited. Switching to a better CPU speed makes more performance gain on AMP code than overclocking the GPU. Kind of odd :/
Ryan Smith - Wednesday, November 21, 2012 - linkIf I remember the MS presentations correctly, GPU entry and exit is rather expensive. If you try to maximize the amount of time you stay on the GPU, you might see better results.
IanCutress - Wednesday, November 21, 2012 - linkI rearranged my code to do just that. Maybe I'm just not spawning enough threads.
maximumGPU - Wednesday, November 21, 2012 - linkhave been testing AMP for a couple of months now, and i must say i prefer it to cuda. It definitely feels more C++ rather than C, and makes the conversion of existing C++ work easier. Not "slap code to phi and be done" easy, but i feel it's a step up from cuda.
From a few benchmarks i ran, it's a tad slower (could be application dependent), but i'd happily trade that for the nicer language.
Would be nice to hear your thoughts about it.
smike - Wednesday, November 21, 2012 - linkHi, I love listening to your podcasts and learn a lot every time. Unfortunately, they're very long and I dont always have time to listen to the whole thing. I'd like to suggest that you add the ability to increase the playback rate of the audio for people like me.
document.getElementsByTagName('audio').playbackRate = 1.5;
Peanutsrevenge - Wednesday, November 21, 2012 - linkOMG Anand, -100 geek points for you, now go sit in the corner and think about your newbness.
HOW can you not have heard of cCleaner, it's a geeks favorite application (Glary utilities is similar but in testing curently).
Please don't now hit me with a bunch of software you use all the time, my brain will explode :D
Anand Lal Shimpi - Wednesday, November 21, 2012 - linkHa! In my defense, I tend to just build more systems instead of dealing with existing ones. It gives me an excuse to use new hardware in real world scenarios for extended testing, and often results in me finding issues I wouldn't have otherwise.