wombat23
./llama.cpp/build/bin/llama-server \
-c "$context_size" \
-ctk q4_0 \
-ctv q4_0 \
--no-models-autoload \
--models-dir ~/bonsai \
--reasoning-preserve \
-ngl 99
the max context size i could serve is 64K on GPU only (the -ngl 99 setting). tested with pi harness and it is very fast. the /thinking level always gets reset to off though and it is not very smart like this. haven't figure out a way to fix that. -b, --batch-size N logical maximum batch size (default: 2048)
-ub, --ubatch-size N physical maximum batch size (default: 512)
I also tried double the default. that also means that they can be left to default settings, apparently. git clone https://github.com/PrismML-Eng/llama.cpp && cd llama.cpp
cmake -B build -DGGML_CUDA=ON -DCMAKE_CUDA_ARCHITECTURES=86 && cmake --build build -j
Then downloaded & verified `Ternary-Bonsai-2-27B-PTQ1_0.gguf` from HF and ran ./llama.cpp/build/bin/llama-cli -m Ternary-Bonsai-2-27B-PTQ1_0.gguf -ngl 99 -fa on -c 32768 -b 256 -ub 64 --temp 1.0 --top-p 0.95 --top-k 20 -ctk q8_0 -ctv q8_0 -p "hello world in x86 assembler" -n 256
the parameters were suggested by gpt-5.6-luna to reduce memory footprint, as the defaults ran OOM on my gpu. result looks good: [ Prompt: 165.6 t/s | Generation: 40.6 t/s ]
would be nice if they upstreamed their changes so that it runs with the original llama.cppLast week-end I was exploring the current possibilities of automated Ghidra analysis with Codex. My first attempt derailed quickly, but after giving it the pyghidra documentation, it reliably wrote Python scripts that would alter data types etc. exactly how I wanted, but based on fixed rules.
My next goal would be to incorporate LLM decisions into the process, e.g. let the LLM come up with a guess at a meaningful function name to make it easier to read, stuff like that. I made a skill for this functionality and let Codex plough through in agentic mode. I stopped it after a while as I was not sure what it was doing, and I didn't have more time to work on it since. I would need to do some sanity checks on the ones it has already renamed.
Would be curious what workflows others have already devised? Is MCP the way to go?
Is there a place where people discuss these things?
You do need to start at 20% capitalization though, which at current prices means they need to own assets already (market risk), or have bonkers amounts of currency sitting around (inflation risk). I understand the FOMO some people must have.
I wonder if ultimately there is a cascade happening, where increased valuations lead previous owners to either take new mortgages, or sell their old house, and pay more for a new one. Which creates a cycle of ever increasing prices? I've never read anything though whether such an effect exists.
care to elaborate?
IMO, there should be some kind of archive that conserves and publishes them after some time has passed, so that they could be ported to new hardware and kept accessible. and somehow documented for future historians.
https://www.sciencedirect.com/science/article/pii/S096098222...
Current neuromorphic hardware is not easily accesible, but you can simulate spiking neural networks. Check out, e.g. https://brian2.readthedocs.io/en/stable/ or Nengo.ai
Empirically, you could have bought a share of the SPX at any point in time, and sold it with profit later. The real problem is what happened in the time between, and whether you were able to hold on.
> If you want to make progress in any area, you need to be willing to give up your best ideas from time to time. [...] Medawar notes that he twice spent two whole years trying to corroborate groundless hypotheses.
Unfortunately, being willing to scrap your idea is only one part of the equation. Securing funding after 2 "failed" post-docs is an entirely different matter.
-> Classically, there are 3 spatial dimensions (directions of movement) with Euclidean metric, and all the classical laws (Newton's laws, gravity, etc.). Quite successful, but breaking down in extreme cases (high energy, ie. velocity/mass/etc). +there is a whole range of seemingly unrelated laws necessary.
-> with relativity theory (both special and general), time becomes a 4th dimension, but it has a special status in the metric (opposed sign), making spacetime non-Euclidean. One effect of this is suddenly you don't need a law of gravity anymore. Things just follow geodesics in this space. It also explains some effects that could not be derived from classical gravity. Essentially explaining more phenomena with less "overhead", in exchange for more dimensions.
What Ever Happened to the Couch Potato? (2016)
My memory is a bit fuzzy about the details, maybe it was about the inner margins of left-hand side and right-hand side changing. Maybe someone else recognises what I mean? :)
Since Latex is very powerful, I'm sure there is a way to code that behaviour in. But I had spent too many hours already on that project and I was happy with the result anyway, so I stopped investigating.
On the technical side, it wasn't so straightforward to me to get a good result. In my case, I had to iterate a few times and order a new copy with adjustments to margins, etc. until it looked right.
One issue I didn't manage to solve back then was that the inner margin needs to slightly increase towards the end of the book. That's because the binding is eating up visual space since you can't open the book flat without destroying it. Professional publishing tools do this automatically, but Latex doesn't have an option for it. At least that's how I remember the issue. But maybe things have changed?
I see the corporate aspect of F#, but can you elaborate on what you mean by "special" about Haskell?
It looks to me like they would satisfy the same points that the article makes.
Edit: just did a quick comparison of the last 2 SO developer surveys, and it looks like Haskell "replaced" F# in their popularity ranking last year.
But I also feel like the language is mainly used in a type of business environments that are already tied to .NET infrastructure anyway, and who actually appreciate the interlock.
And it could get much more traction outside of that circle, especially in the open source world.
I think .NET can be quite an advantage, as stated also in the article.
but if I want to, say, set up a dev environment on linux, it comes with a set of quite different dependencies than what other languages use.
It's funny because that's exactly how I felt when I learned F#. I felt pleasantly surprised and never felt like there was anything bad about the language itself.
I just wish it wasn't so deeply embedded in the .NET ecosystem.
Does anyone have some resources to learn how (UNIX) terminals work under the hood and how one can achieve nice graphic effects with it?
Also, is ncurses still the go-to solution, or do people use something like termbox or something else?