This is very heavy on disk and CPU and goes through the database server a heck of a lot. It has some massive tables and tons of files, generating a backup around 380MB. Back up a medium-sized Joomla 4 site, created to mimic the characteristics of our business site ( ).This uses Phing to create Joomla installation ZIP files for each library, module, plugin and the Akeeba Backup component itself, finally placing them all in a ZIP package with a generated XML manifest. Build the Akeeba Backup installation package from sources.I decided to run my own benchmarks, timing typical workloads in my working day: Answering support tickets and emails, using the web, using Messages, all the little stuff was fast too. PhpStorm felt much more responsive and enjoyable, without having to quit and reopen it every hour. That was strange.Īs it happened, I was in a middle of a large scale code refactor I had started on my MacBook Pro which I continued on the M1. Installing software so so fast that I couldn’t keep up, finding the various DMGs and whatnot, instead of the Mac not keeping up with me. I sailed through the macOS installation without any of the familiar “are we done yet” pauses I knew from the Intel-based Macs of yore. Then, I received my Mac mini M1 on January 4th, 2021.Īs soon as I turned it on it felt… snappy. I had already placed a non-cancelable, non-refundable order for my customised machine so I was just sitting here, thinking that I have either made an expensive mistake or a great decision - something which would have to be determined in hindsight. I thought there’s not a snowball’s chance in Hell that it’d be in the same ballpark. So when I saw the benchmarks imply that the 1400 Euro Mac mini M1 would be in par, if not a little slower, than a 4300 Euro mid-2019 MacBook Pro 15” with an Intel Core i9-9980HK I was dubious. They are an arbitrarily weighed average of arbitrary tasks that may or may not have relevance to real world workloads, trying to measure the sustained (as opposed to peak) performance of just the CPU with total disregard to how everything else in the system is tied together. Of course, synthetic benchmarks are largely a lie when it comes to real world usage. More in-depth technical analysis of the microarchitecture also hinted at a machine that is likely to perform very well despite being an ARM-based design (or exactly because it’s an ARM-based design, if we’re talking about the unheard of 8-wide decoder). They seemed to confirm that it’s a speedy processor. In the meantime, I was looking at early benchmarks. Selling it after a few months and losing a few hundred Euros? I can live with that gamble. “What’s the worst case scenario?”, I thought to myself. Knowing that any choice I made would be final - no user upgradeable, or even accessible, parts are present on this machine - I decided to order a customised Mac mini M1 (16GB RAM, 512GB SSD) in November, as soon as the orders opened in my country. Would that experience translate well to building a desktop-class processor and GPU? These devices also have relatively spartan amounts of RAM when compared to desktop-class machines, relatively small screens and are essentially running one application at a time. Sure, they have been making their now processors for the iPhone and iPad and I have first hand experience of their amazing performance… as far as mobile devices go. When Apple announced their plan to transition to their own processors I was equal parts excited and sceptical. Just to give you an idea: it’s a monster worth every penny of its modest price. I would like to talk about it in the context of web development. There’s been a lot of speculation and conflicting information about its performance. Two weeks ago I finally received a Mac mini M1 with the brand-new, ARM-based M1 (Apple Silicon) processor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |