Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Friday December 02 2022, @04:50PM   Printer-friendly

TSMC's Arizona Plant Will Build Apple's 4nm Chips Starting In 2024:

The new $12 billion TSMC plant in Arizona will start to produce Apple's 4nm chips starting in 2024, with the iPhone maker being key to pushing the production forward.

But Apple and other companies wanted to be able to source 4nm parts from the United States, with TSMC relenting.

TSMC previously said it would make 20,000 wafers per month at the Arizona facility, although production may increase from those original plans, the people said. Apple will use about a third of the output as production gets underway.

Apple's most current chips are all produced on a 5nm process and the move to a new 4nm process could allow for improved performance, reduced power draw, and better thermal management. The chips will likely be used in iPhones, iPads, and Macs while Apple's future products could also make use of the technology.

Apple and other major tech companies rely on TSMC for their chipmaking needs, and the change means they'll be able to get more of their processors from the US. Apple Chief Executive Officer Tim Cook has previously told employees that his company plans to source chips from the Arizona plant.


Original Submission

 
This discussion was created by janrinok (52) for logged-in users only, but now has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Saturday December 03 2022, @10:54AM (3 children)

    by Anonymous Coward on Saturday December 03 2022, @10:54AM (#1281005)

    https://soylentnews.org/comments.pl?sid=52490&cid=1280925 [soylentnews.org]

    Right now, the backend is mostly built on an outdated version of mod_perl 2.2, and MySQL cluster, which is very much not a good place to be.

    Jarinrok previously implied that MySQL had nothing to do with the data loss when I said this site was an example of why not to use MySQL.

    Well if MySQL wasn't responsible then it means the wetware involved is even worse... 😉

  • (Score: 2) by RS3 on Saturday December 03 2022, @04:01PM (2 children)

    by RS3 (6367) on Saturday December 03 2022, @04:01PM (#1281016)

    I'm curious, what's your direct experience with MySQL, including versions (or years for general reference)?

    Other database engines?

    Which would you recommend?

    • (Score: 1, Informative) by Anonymous Coward on Sunday December 04 2022, @05:53AM (1 child)

      by Anonymous Coward on Sunday December 04 2022, @05:53AM (#1281099)

      At a previous workplace we did use MySQL. It was crap - too high chance of data loss or corruption (for example they've had too many bugs where the DB sorts in a wrong order ). Sure it had lots of features you could check off on the "brochure". But in practice many features/advantages exclude the other features - you can't have them at the same time. MySQL is the PHP of databases. There's no good reason to use it other than "legacy".

      For my choice- PostgreSQL. Haven't had DB caused data loss (e.g. caused by Postgresql whether directly or indirectly). Yeah it has bugs too but it's definitely not as buggy and crappy as MySQL.

      Not my choice, current workplace - MS SQL. Haven't had DB caused data loss but SQL Server 2019 seems crappier and buggier than usual[1]. The earlier versions seemed solid enough in terms of the backend DB stuff. But I don't really like the dialect of SQL it uses (Transact SQL)- all those square brackets really look ugly.

      [1] https://support.microsoft.com/en-us/topic/kb4538581-fix-scalar-udf-inlining-issues-in-sql-server-2019-f52d3759-a8b7-a107-1ab9-7fbee264dd5d [microsoft.com]

      • (Score: 2) by RS3 on Sunday December 04 2022, @07:05AM

        by RS3 (6367) on Sunday December 04 2022, @07:05AM (#1281102)

        Wow, thank you for an awesome answer. So far I've had no problems with MySQL, but honestly the sites I'm running (for someone who owns the site, servers, etc.) are fairly low traffic, fairly small amount of data. The customers are using WordPress as a website builder, not as a true blog or forum, so the database doesn't really grow a lot. Although I'm sure I could support and scale it if needed. That's pretty easy, but not if MySQL borks. I'm not on the very newest version either.

        There's an automated cron.daily backup, and for a site like this I'd do maybe hourly incremental (as long as it can be restored easily!)

        Something in the Apache - php - MySQL chain is a bit inefficient. I haven't put a lot of effort in tracing it, but I'm pretty sure it's php slowing things. Static Apache pages are instant, and I don't have varnish or squid or anything like that running, and I don't have php-fpm properly set up yet, but I will with the new server. There are caching plugins for WordPress which cache the output of the php interpreter. I'm using one or two here and there, but there are better ones out there that I'm researching.

        It's by far not my main job, and I'm spread a bit thin, but soon I'll dig into it and get everything integrated and tuned.

        As I mentioned (somewhere...) I'm building up a new server and I might go with PostgreSQL. I think I used it for Drupal or Joomla or maybe it was a real estate sales / management system that used it.

        A lot of people rail against php, but again, I don't see any problems. Well, it's a bit slow, as most interpreted languages are, and I haven't done any real coding in it- just a few code tweaks. I dunno...

        BTW, as you may know, MySQL has many internal "engines", so maybe you were using one that happened to be problematic? I think InnoDB is the most used, "ACID" compliant, etc.