You mean to tell me that a $2000 Macbook is almost as performant as a $1000 PC? Tell me more!
Apple’s M1 processor and the full 128-bit integer product
101–110 of 180 posts
Re: Apple’s M1 processor and the full 128-bit integer product
#102Earlier quoted context omitted.
I am seeing lots of spinning balls with 1Password on my 2015 Macbook Pro. Even just switching between fields with the keyboard brings up a spinner for two seconds or so. It's a recent thing I think. No other app has any issues.
Is it possibly due to the x86 emulation? I could see something like that being the cause
I see the same thing on native x86 1Password.
Re: Apple’s M1 processor and the full 128-bit integer product
#103Earlier quoted context omitted.
Not in the next 10 years. Why would they? Fabs are extremely capital-intensive and take years to get up and running, when (like Taiwan Semi) knows how to do it. Intel has shown how hard it can be to do this right. Let TSM work on production (and hopefully get more/larger fabs in the USA up and running) and getting better at packing in the transistors, and let Apple improve the design (and software).
Because of the non-zero chance of Southeast Asian fabs becoming suddenly unavailable.
This. It's not a money-making play; it's a catastrophic insurance policy.
Re: Apple’s M1 processor and the full 128-bit integer product
#104I love my M1, but does anyone else have horrific performance when resuming from wake? It’s like it swaps everything to disk and takes a full minute to come back to life.
This is anecdotal and I don't have anything to prove it, but I really feel like my old spinning-hard-drive 2010 MacBook Pro woke faster from sleep running Snow Leopard, than the Retina models ever did (or the old ones did after a few software updates). Of course for general tasks it was slower, but I really remember that thing waking up instantly when I raised the lid, every time.
My nostalgia agrees with you, but I think it’s probably wrong. The wake from sleep was what finally convinced me to get my first Mac. Even now they have the best hibernation and wake from sleep.
Re: Apple’s M1 processor and the full 128-bit integer product
#105I love my M1, but does anyone else have horrific performance when resuming from wake? It’s like it swaps everything to disk and takes a full minute to come back to life.
I am using the LG Ultrafine 5K (so it’s a TB monitor) and it takes maybe 1.5s to 5s longer than the built in display (which wakes instantly) to turn on.
I do occasionally have an issue where the brightness on the built in display is borked and won’t adjust back to the correct level for anywhere between 30s to a few minutes.
And then I don’t know if it’s my monitor or the M1, but sometimes there will be a messed up run of consecutive pixel columns about 1/10th of the screen wide starting about 30% from the left of the display. The entire screen in that region is shifted a few pixels upwards. Sometimes it’s hard to notice it but once you do it can’t be unseen. Replugging the monitor into the M1 resolves the issue.
Re: Apple’s M1 processor and the full 128-bit integer product
#106Earlier quoted context omitted.
Instant wake for me. However any time I come across a password field in a website the computer freezes for a painfully long 10 seconds or so while it presumably decrypts my password vault. Sometimes this will happen multiple times per page load if I deselect and reselect the password field.
Oh goodness I thought this was just me after searching online and finding very little, if any, discussion of the bug. The issue I had wasn't on password login prompts, but on account creation prompts (i.e. password+confirm password). I had assumed it was lastpass at first, but the freeze persisted even after removing that -- on a one-day old computer.
Feel free to report it in Feedback Assistant.
Re: Apple’s M1 processor and the full 128-bit integer product
#107Re: Apple’s M1 processor and the full 128-bit integer product
#108Did anyone actually look at the machine code generated here? 0.30ns per value? That is basically 1 cycle. Of course, there is no way that a processor can compute so many dependent instructions in one cycle, simply because they generate so many dependent micro-ops, and every micro-op is at least one cycle to go through an execution unit. So this must mean that either the compiler is unrolling the (benchmarking) loop,…
Failing to post disassembly for a micro benchmark is annoying.
It is of course speculating all the way through the loop; a short backwards conditional branch will be speculated as "taken" by even very simple predictors.
Op fusion is very likely, as is register renaming: I suspect that "mul" always computes both products, and the upper one is left in a register which isn't visible to the programmer until they use "mulh" with the same argument. At which point it's just renamed into the target register.
Re: Apple’s M1 processor and the full 128-bit integer product
#109Earlier quoted context omitted.
I am seeing lots of spinning balls with 1Password on my 2015 Macbook Pro. Even just switching between fields with the keyboard brings up a spinner for two seconds or so. It's a recent thing I think. No other app has any issues.
Is it possibly due to the x86 emulation? I could see something like that being the cause
Apparently the latest version 7.8 runs natively on Apple Silicon.
Re: Apple’s M1 processor and the full 128-bit integer product
#110Earlier quoted context omitted.
Is it possibly due to the x86 emulation? I could see something like that being the cause
I see the same thing on native x86 1Password.
I just updated to version 7.8 from version 7.7 and it looks fine so far. I haven't seen any freezes in the five minutes that I have been using it.
This makes me realise how much of a pain it has been to use in the past weeks or so. Now that it is back to normal snappy it is such a pleasure to work with again.