AMD are also doing a good job. The 7000s look very good. Crazy that this is still on a larger process node than Apple.
936 karma · joined August 27, 2012
AMD are also doing a good job. The 7000s look very good. Crazy that this is still on a larger process node than Apple.
https://www.notebookcheck.net/Dell-XPS-13-Plus-with-i7-1280P...
Note that that is a 12th gen P. I suspect the U CPUs won't perform quite as well but will offer much better battery life than the MBP.
Unfortunately Lenovo or Dell might get my budget if it looks like that's not going to happen for a while. This laptop has had a few too many drops off of my bike (which is why repairability would be great!).
Also - unnecessarily gendered title?
Still handicaps them compared to Nvidia where you can just buy anything recent and expect it to work. Suspect it also means they get virtually no open source contributions from the community because nobody can run or test it on personal hardware.
AMD don't seem to even be trying on the software-side at the moment. ROCm is a mess.
https://twitter.com/sstephenson/status/1388146129284603906
https://twitter.com/ThatDetroitAndy/status/13881952733364019...
https://twitter.com/georgeclaghorn/status/138813100953171968...
https://twitter.com/lexicola/status/1388189598367559688
https://twitter.com/zachwaugh/status/1388190748189802501
https://twitter.com/sophaskins/status/1388155262972874754
https://twitter.com/jonasdowney/status/1388205182916440070
https://twitter.com/Rahsfan/status/1388209146487623681
https://twitter.com/kikiaards/status/1388208900608954371
https://twitter.com/mackesque/status/1388206605506842627
https://twitter.com/wcmoline/status/1388208323908968449
https://twitter.com/RossRochford/status/1388202323718115329
https://twitter.com/conormuirhead/status/1388207801646780416
13 resignations today by my count.
Been 1ms for a few months now. =)
M1: https://images.anandtech.com/doci/16252/latency-m1_575px.png
Zen3: https://images.anandtech.com/doci/16214/lat-5950.png
If anything the M1's ram has _higher_ latency than the Zen3.
(Can't reply to the sibling comment but Intel's numbers are even better: https://images.anandtech.com/doci/16214/lat-10900.png)
A few questions.
How big do you foresee your constellation being?
How fair is the comparison in your Google Photos link? The image on the right seems to have significant artifacting that looks more a side effect of compression.
Colab Pro isn't available outside the US (without breaking Google's terms).
When I think about OSS databases for example I can't think of any widely used ones that don't have at least one commercial entity that provides maintenance and support which funds development.
Don't get me wrong. It would be great if Elastic, Redis and co didn't have to do this (change license) but AWS does pose an existential threat to their business models long term. I'd rather a standardised, so there's less fear around interpretations, more restrictive license than the businesses and _future_ ones becoming unviable.
I would say Google's approach of partnering with maintainers instead of competing with them is healthier, though only just.
Elastic's changing their license. No contributions are being stripped of their open source license. You always have the last open source licensed version to go back to and fork if you like.
What this author is upset about is that Elastic are no longer providing updates under a license the author feels they are entitled to.
Maybe the author should fork the project and maintain it under an open license themselves?
The store to the address at rsi will actually go in to the processor's store buffer and the subsequent add is allowed to retrieve the value from the store buffer _before_ it's drained to main memory.
Under TSO, AMD's memory mirroring implementation here is totally fine.
It could potentially change observable behaviour if you could turn it on or off but this is irrelevant given you wil see changes in observable behaviour for that same snippet of code depending on which microarchitecture of AMD or Intel processor you choose to run it on.
It's worth having a read on the details for different memory models and how they relate to implements. This seems like a good guide: https://www.cs.utexas.edu/~bornholt/post/memory-models.html
I'm saying people shouldn't look at this decision as "Apple has our interests in mind" but rather "in this particular case Apple's self interested is aligned with our own because of their business model".
Apple no longer has an ad network which means it can't take it's cut from ad revenue. By reducing the effectiveness of ads on the platform it pushes more people to in app purchases which it receives a heft chunk of.
Most common Lempel-Ziv compressors (gzip/brotli/zstd) use some form of entropy encoding (Huffman/Arithmetic/ANS) but that is in addition to lz algorithm (usually lz77) itself.
You can have a Lempel-Ziv compressor that doesn't use entropy encoding, look at something like lz4.
lz77 essentially works by copying parts of the recent window of decompressed data. e.g if a phrase of length 10 was used 100 characters ago we could encode 100,10 instead of the phrase itself. Most compressors use entropy encoding on those offset and length streams.
Do you have control over that?
If anything AWS' Graviton2s are competitive on multithreaded workloads and it looks like the Neoverse cores are only going to improve there.