HN user

galeos

817 karma
Posts39
Comments39
View on HN
github.com 1y ago

1.58bit LLM Optimised Tensor Core

galeos
2pts0
github.com 1y ago

BitNet 1.58bit GPU Inference Kernel

galeos
2pts0
techcommunity.microsoft.com 1y ago

Microsoft beat H200 Deepseek inference with MI300

galeos
3pts1
www.eetimes.com 1y ago

Modular's CUDA alternative is ready

galeos
2pts0
arxiv.org 1y ago

BitNet b1.58 2B4T Technical Report

galeos
111pts30
huggingface.co 1y ago

Microsoft BitNet 1.58bit LLM 2B4T released

galeos
2pts0
huggingface.co 1y ago

Mi300 Huggingface

galeos
2pts0
arxiv.org 1y ago

Bitnet.cpp: Efficient Inference for 1.58bit LLMs

galeos
1pts0
arxiv.org 1y ago

Matryoshka Quantization

galeos
2pts0
arxiv.org 1y ago

1-Bit AI Infrastructure

galeos
157pts30
github.com 1y ago

Microsoft BitNet: inference framework for 1-bit LLMs

galeos
173pts33
www.bloomberg.com 1y ago

Apollo to offer Intel multibillion-dollar investment

galeos
5pts3
huggingface.co 1y ago

Fine-Tuning LLMs to 1.58bit

galeos
52pts3
www.nature.com 1y ago

Evidence of dark oxygen production at the abyssal seafloor

galeos
9pts0
www.lamini.ai 2y ago

Lamini Memory Tuning: 10x Fewer Hallucinations

galeos
128pts57
nostarch.com 2y ago

Computer Architecture – No Starch Press

galeos
2pts0
huggingface.co 2y ago

Extracting Concepts from LLMs: Anthropic's recent discoveries

galeos
4pts0
morethanmoore.substack.com 2y ago

AMD Announces Instinct MI325X Today, CDNA4 to Come

galeos
2pts0
www.phoronix.com 2y ago

AMD and Intel Team Up for Open Alternative to Nvidia's NVLink

galeos
38pts6
learn.microsoft.com 2y ago

Azure – ND AMD MI300X v5-series

galeos
2pts0
huggingface.co 2y ago

Hugging Face on AMD Instinct MI300 GPU

galeos
2pts0
www.bbc.co.uk 2y ago

Bristol University to receive £225M to create UK's new supercomputer

galeos
4pts1
www.thelancet.com 4y ago

Hunt begins for the cause of acute hepatitis cases

galeos
1pts0
www.eurogamer.net 4y ago

Return to Monkey Island Announced

galeos
2pts0
obedparla.com 4y ago

A Visual Guide to React Mental Models

galeos
2pts0
www.bloomberg.com 4y ago

DOJ Seizes $3.6B in Bitcoin Stolen in 2016 Bitfinex Hack

galeos
7pts0
www.onionfutures.com 4y ago

Turning off Bitcoin’s inflation funded security model: wishful thinking?

galeos
3pts4
www.onionfutures.com 4y ago

Bitcoin's 21M coin cap is not guaranteed

galeos
2pts2
www.thelancet.com 5y ago

Experts call to include prisons in Covid-19 vaccine plans

galeos
1pts0
www.bloomberg.com 5y ago

Tokyo stock exchange network issue

galeos
6pts1

In the UK the tax incentives for Electric cars may be skewing demand towards new Vs secondhand EVs.

I can lease a new EV via my employer's salary sacrifice scheme. I can pay my lease payments from my pre-tax income. There is an additional tax due on cars leased this way in the UK called Benefit-in-Kind tax (BIK). The rate of this tax is fairly high for petrol/diesel cars but for EVs is currently near zero (based on 2% of the car's value).

The problem is that most of the major lease firms that operate these programs for employers only offer new vehicles. Ideally I would like a nearly-new EV. I have escalated and apparently our lease provider (Tusker) are looking at rolling this out in the first half of this year. I currently know of only one other lease firm that offers this option. I suspect is in the interest of lease firms to prop up the value of the used EV market, but this depends also on their margins on new vehicles. I wonder if it would make sense for the tax incentives for used Vs new EVs to be rejigged to avoid incentivising unnecessary new car production?

Relatively fast onset gastro symptoms. Used to be fine with any beer but at about 21 started noticing the problem with a lot of largers. Asahi, Tsing Tao, seemed less of a issue. Not formula diagnosed.

I appear to have a yeast intolerance that stops me drinking some (but not all) beers. I can drink Guinness though! I didn't realise it used a distinct strain of brewers yeast. If only breweries listed the yeast they used in the ingredients, I could narrow down which one(s) are problematic...

That's funny. I went for an open day in the UK Computer Science dept in 1999. It was an exciting department but one of the things that put me off was the internet was so slow in the lab it was almost unusable. Perhaps they were having a bad day...

I was too young to read the Rudiments of Wisdom comics. My mum cut them out and saved them in a scrap book for me. She finally gave me it about 10 years later, in the mid 90's, to read. What a treat!

I suppose that might be true, but we can imagine a situation where there is no choice in the matter:

If network security cannot be maintained without sufficient inflation, then it surely it doesn't matter how philosophically wedded some users are to the 21m cap. It would lead to a hard fork, with two resulting coins:

1. An unchanged 'Capped-supply Bitcoin' 2. A new 'Permanent-subsidy Bitcoin'

Given a total breakdown in network security of the 'Capped-supply Bitcoin' (and its associated collapse in value), we would expect users to deem the, still secure and therefore higher value, 'Permanent-subsidy Bitcoin' to be the 'true' Bitcoin going forward, no?

Network difficulty adjustment is there to ensure we get a new block mined, on average, every 10 minutes. It does not impact the cost of a 51% attack, just the block mining rate.

As emissions drop, less money is spent on mining and a 51% attack becomes cheaper.

When China turned off mining, mining temporarily became more profitable as it took some time for miner spend to get back to a equilibrium state (where miners, in aggregate, spend nearly the entire block reward on mining costs).

It did temporarily get 'cheaper' to conduct a 51% attack (although it was still so expensive as to not be viable - due to the currently high block reward). This wasn't because of the difficulty adjustment though - that just maintained the average time to mine a block at 10 minutes.

In the late 90's I went for an interview at a Sony store in London. At the start of the interview the store manager told me that he had been busy preparing the shop's regular report of addresses of everyone who had purchased a new TV for TV licensing. I imagine these were then cross-referenced against who had a TV license for potential follow-up. I struggle to see how the idea of TV detector vans were more than 'enforcement theatre', although possibly a cheap and effective strategy in the past.

While I wouldn't deny the Google has a poor reputation for customer support across their product range, I can report a notable exception - my Google Pixel (1) phone purchased from the Google Store in 2016. Every time I have had an issue I have utilized the phone's support chat service. I have always been connected to a live support agent in less than a minute. Whenever I have had any issues, I have been sent a replacement handset next-day, including twice after my 2 year warranty expired. The most recent of these episodes was last month.

While most of the focus here is understandably on the CPU side, there seems to be some interesting shifts taking place on the GPU side.

AMD currently has a process lead over Nvidia (and this is rumoured to be set to continue for a little while longer - apparently the first consumer Ampere chips are being fabbed on Samsung's inferior 8nm process due to lack of capacity at TSMC for the next few months)

Nvidia has clearly had an architecture advantage, although RDNA2 may close this gap, depending on how Ampere performs.

While Nvidia has had a much stronger showing in the GPGPU space, with CUDA helping it be the clear current winner, this also appears to have driven architecture decisions at Nvidia with the focus on tensor cores.

In gaming, Nvidia has put a lot of work into utilising these tensor cores for Deep Learning Super Sampling (DLSS). The idea being that you render at a lower resolution and then use deep learning to upscale in real-time to higher resolutions. DLSS 2.0 made some leaps in quality and DLSS 3.0 is on the horizon. It will be interesting to see:

a) How well they can get this working b) Is AMD working on its own version of this? c) If so, how well will the RDNA architecture be suited to this approach?

Will be interesting to watch how this plays out!