This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
2012
editWell, it's 2012. Anyone with news? — Preceding unsigned comment added by 187.113.201.87 (talk) 02:44, 20 January 2012 (UTC)
Power efficiency
editThe beginning of the article says "In addition to being 55% faster than K, IBM Sequoia is also 150% more energy efficient." and in the end "The Sequoia design will perform 3000 Mflops/watt, about 7 times as efficient as the Blue Gene/P design it is replacing, and more than 3 times as efficient as the current (as of June 2011) Top 500 leader.". So 150% or 3 times ? --Martvefun (talk) 07:15, 19 June 2012 (UTC)
- Also, the beginning of the article says "Sequoia is also more energy efficient, as it consumes 7.9 MW", but in the last section, it says that Sequoia uses nearly 6 MW of power. I will try to figure out which it is, 7.9 MW or slightly less than 6 MW! --FeralOink (talk) 13:04, 17 July 2012 (UTC)
Sockets are not cores are not sockets
editThe article had originally said 123% more (ie 2.23 times) sockets than the K Computer (previous record holder), however the cite given refers to cores. The numbers stack up based on cores ie 705024 vs 1572864. Sockets is generally used to refer to the number of socketed CPU packages, which these days are typically multi-core, but core density per socket varies, so it can be a useful number. For what it is worth, the K computer has 8 Core Sparc VIIIfx CPUs, so 88,128 sockets whereas the Sequoia has 16 core PowerPC A2s, so 98,304 sockets. However, I suspect that the CPUs themselves may not be socketed as such, possibly surface mounted. 60.240.207.146 (talk) 12:56, 20 December 2012 (UTC)
External links modified
editHello fellow Wikipedians,
I have just modified 5 external links on IBM Sequoia. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://www.webcitation.org/69mzfDhru?url=http://www.top500.org/lists/2012/06/press-release to http://www.top500.org/lists/2012/06/press-release
- Added archive https://web.archive.org/web/20101201143722/http://top500.org/system/ranking/9900 to http://top500.org/system/ranking/9900
- Added archive https://web.archive.org/web/20110807145429/https://hpcrd.lbl.gov/scidac09/talks/Seager-Sequoia4SciDACv1.pdf to https://hpcrd.lbl.gov/scidac09/talks/Seager-Sequoia4SciDACv1.pdf
- Added archive https://web.archive.org/web/20141031152502/http://zfsonlinux.org/docs/LUG11_ZFS_on_Linux_for_Lustre.pdf to http://zfsonlinux.org/docs/LUG11_ZFS_on_Linux_for_Lustre.pdf
- Added
{{dead link}}
tag to http://www.green500.org/lists/2011/06/top/list.php - Added archive https://web.archive.org/web/20110526004140/http://www-304.ibm.com/jct03004c/press/us/en/pressrelease/26599.wss to http://www-304.ibm.com/jct03004c/press/us/en/pressrelease/26599.wss
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}}
(last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 01:09, 10 November 2017 (UTC)
usefulness
editno data on idle time , no data on offline storage, no data on error correction, no data on if SIMD or MIMD machine, or front end, or failure of linux to support realtime processing.
no data on security faults, down time, diagnostics, ok im tired ill stop Juror1 (talk) 13:41, 15 November 2017 (UTC)