Anyone else think that CPU manufacturers should focus more on speed than si


Recommended Posts

I personally do not care how much power it consumes and it is usually only a few watts difference. I rather them focus on instead of trying to make the CPU smaller instead keep it the same size and focus on making it faster..... What do you guys think?

Right, they go hand in hand. Smaller fab processes means less power, means less heat, means more speed possible. It's not like they've stopped getting faster.

  • Like 1

Making the cpu smaller does increase speed. One example is the xbox 360 cpu. When they shrank the size of the cpu it actually made it faster. They had to artificially limit the cpus to make them the same speed as the older 360's so everything was compatible.

CPUs have been more than fast enough for most use cases since the introduction of the Core2Duo back in 2006 at latest. I don't mind slight speed increases, sure; but I'd rather Intel and AMD keep focusing on making their CPUs use less power. Remember the insane power usage of the Pentium 4 class CPUs? We really don't need to go back there.

There's no need to focus on speed any more. Even the i3s are more than fast enough to cope with anything pretty much that you won't ever max out a single core - gameplay wise this certainly holds true. You can have a pretty cheap and relatively poor processor in there that won't bottleneck the system.

I personally do not care how much power it consumes and it is usually only a few watts difference. I rather them focus on instead of trying to make the CPU smaller instead keep it the same size and focus on making it faster..... What do you guys think?

You obviously haven't installed a socket 2011 CPU then. Those things are huge compared to previous processors. The only one that I can remember that was around the same size was the original Pentium Pros.

  • Like 2
You obviously haven't installed a socket 2011 CPU then. Those things are huge compared to previous processors. The only one that I can remember that was around the same size was the original Pentium Pros.

Well, considering the number of cores they could have in them, it's not so bad. How about Slot 1 CPUs? Hahaha

The actual processor size on the slot 1 was actually tiny. They just sat on a riser card of sorts with cache on the card (hell I still have several of those in a drawer... why... I'm still not sure, lol!)

800px-Celeron_300A.jpg

The actual processor size on the slot 1 was actually tiny. They just sat on a riser card of sorts with cache on the card (hell I still have several of those in a drawer... why... I'm still not sure, lol!)

800px-Celeron_300A.jpg

Precisely.

The S370 merely did away with the riser card - other than the number of pins, the S370 socket was functionally no different from Socket 7.

Slot - 1 was designed deliberately to muck up AMD (since AMD had nary a right to make S1-compatible CPUs - however, they could make CPUs compatible with Socket 7).

They're improving speed, but the truth is, most tasks don't need it. So it's better if they use less power and produce less heat.

Because the one area that demands both is not the *desktop* market - it's portable computing. (Not just tablets and slates, but notebooks, Ultrabooks, and even the semi-traditional laptop.)

That is, in fact, what drove the design of Ivy Bridge - not desktops.

Look at the Ivy Bridge SKU plan - the greatest number of IB SKUs are in the mobile/portable/embedded space - and most of these are i5-S and I5-T. (Fact - there are more i5-S and I5-T SKUs planned than i3 and i7 IB SKUs planned combined.)

That means that IB is not just the CPU for *the rest of us* - it is planned to be the CPU for the *mobile/portable* rest of us.

Sensible for Intel - for two reasons. First - Atom has been a bomb; if anything, it's been an energy-hungry fizzle.

Second - portable computers are actually *replacing* desktop computers as the default computer. (Result - portable computers are needing to do desktop-computer-type tasks.)

*That* means a quad-core - and a portable one that is an energy-sipper by current standards.

You obviously haven't installed a socket 2011 CPU then. Those things are huge compared to previous processors. The only one that I can remember that was around the same size was the original Pentium Pros.

Out of curiosity, I pulled a few out to look. The Xeon E7 LGA1567s were even bigger than the E5 LGA2011s.

E1rpA.jpg

and heavy :) ... you can do some damage if you were to fling one ... freesbee style :) ...

I thought about this while at the urinal .... a 3D CPU ... how do you say it would look like? well like a cube ... - no pins as they are on the mobo ...

how does the mobo look like you say ... well ... like a skewed pyramid .. however a small tweak to that would be that the cube has a hollow slot inside it, and both the outer shell and inner shell would connect to mobo pins ...

yeah, I know you like that ...

and heavy :) ... you can do some damage if you were to fling one ... freesbee style :) ...

I thought about this while at the urinal .... a 3D CPU ... how do you say it would look like? well like a cube ... - no pins as they are on the mobo ...

how does the mobo look like you say ... well ... like a skewed pyramid .. however a small tweak to that would be that the cube has a hollow slot inside it, and both the outer shell and inner shell would connect to mobo pins ...

yeah, I know you like that ...

Yeah, those old ceramic CPUs were heavy as hell. I remember smashing an old AMD CPU like that, hahahaha.

Again though, the Pentium Pros were so big because of the cache. Under the cap only half is CPU, the other half is cache. That's where die shrinking has helped a ridiculous amount.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!