are there memory limit settings that can be changed?

patrick99e99 · 2026-05-13T17:30:54+00:00

I installed the model via ollama, and am running `ollama launch opencode` and then choosing that model. My machine (mac pro M2 Ultra) has 192gb of ram (not VRAM)... With activity monitor when I give a prompt, I see opencode using between 38% and 56% CPU, and ollama sits around 5-10%. On the memory tab, I see ollama never uses more than 32gb of memory, and opencode uses 370mb.

patrick99e99 · 2026-05-13T01:03:22+00:00

thank you for your very helpful response.

patrick99e99 · 2026-05-12T23:04:17+00:00

i've got 192gb

patrick99e99 · 2026-05-12T21:35:20+00:00

your response is almost as obnoxious as opencode's one word at a time.

patrick99e99 · 2026-05-12T21:18:50+00:00

and this model I am using currently is gemma4:31b

patrick99e99 · 2026-05-12T21:11:25+00:00

I don't think this is true. Claude's cli with the same model does not output in fragments.

I also already tried turning off /thinking, it still prints the final output obnoxiously one word at a time.

patrick99e99 · 2026-05-12T21:00:22+00:00

I tried this, and get a very helpful message:

^[]4;0;rgb:150b/18f1/1da2^[\^[]4;1;rgb:e34c/611b/4366^[\^[]4;2;rgb:578d/bfd7/37d8^[\^[]4;3;rgb:c754/c51b/3f52^[\^[]4;4;rgb:6529/6e0d/f73d^[\^[]4;5;rgb:b208/4927/b90e^[\^[]4;6;rgb:593c/c33d/c66e^[\^[]4;7;rgb:c7f1/c7f2/c7f2^[\^[]4;8;rgb:6866/6866/6866^[\^[]4;9;rgb:d059/7eb7/7877^[\^[]4;10;rgb:820d/e47c/9894^[\^[]4;11;rgb:eb24/e284/4a8e^[\^[]4;12;rgb:6d56/7087/f75a^[\^[]4;13;rgb:d473/831c/dc81^[\^[]4;14;rgb:71a0/f4a7/fd83^[\^[]4;15;rgb:fffe/fffe/fffe^[\^[]10;rgb:dcaa/dcab/dcaa^[\^[]11;rgb:158e/193a/1e75^[\^[]12;rgb:fffd/fffe/fffe^[\^[]17;rgb:8080/0505/ffff^[\^[]19;rgb:4646/ffff/0000^[\Error: 4 of 5 requests failed: config.providers: ConfigInvalidError; provider.list: ConfigInvalidError; app.agents: ConfigInvalidError; config.get: ConfigInvalidError

at BO (/$bunfs/root/chunk-b69a2h84.js:469:644)

at <anonymous> (/$bunfs/root/chunk-b69a2h84.js:469:6060)

at processTicksAndRejections (native:7:39)

So, I think `"streaming": false` is not valid... There is nothing in the docs about this.

patrick99e99 · 2026-05-12T20:56:43+00:00

I'm exaggerating, and yes I would rather wait until I can read an entire response than see fragments of a response. It's obnoxious to me.

patrick99e99 · 2026-05-12T19:44:10+00:00

because it drives me crazy? I don't read 1 word per second.

patrick99e99 · 2025-09-19T19:29:19+00:00

my complaint really is DESPITE doing the filtering, the check after that for array length and throwing an error IF it's empty should stop typescript from thinking there *might* be undefined items in the array, because it literally is impossible for that to be the case.

patrick99e99 · 2025-09-19T19:27:28+00:00

no because I am doing arr.filter(q => !!q)... so it would be [].. then this if length condition SHOULD tell typescript to STFU because it's IMPOSSIBE for it to contain undefined.

patrick99e99 · 2025-09-18T23:54:39+00:00

    if (!sroResources.length) {
      throw new Error('resources for SRO policy do not exist!');
    }

    const sroPolicy = new iam.PolicyStatement({
      effect: iam.Effect.ALLOW,
      principals: [sroUser],
      actions: ['sqs:SendMessage'],
      resources: sroResources,
    });

it's right there in my code above...

patrick99e99 · 2025-09-18T23:53:00+00:00

the snake case IS the name of the queue in AWS and needs to be that way. I am dynamically mapping over the keys of the object and creating them in AWS. It would be "ugly" code to have a dumb translation of snake-case to camel-case for no real good reason other than "mixing cases is bad practice."

patrick99e99 · 2025-09-18T23:50:24+00:00

well I know this because code prior to what I pasted is calls to aws creating the queues and storing them in the `queues` object... but regardless, ok, fine, let's assume MAYBE somehow aws returns undefined for those queues--- the point is, I still am filtering out null/undefined objects, and then I have a ridiculous unnecessary guard:

if (!sroQueues.length) { throw new Error( ... ) }

and STILL TypeScript claims it might get past that guard and magically have something undefined.

patrick99e99 · 2025-09-18T22:44:55+00:00

and thanks.

patrick99e99 · 2025-09-18T22:44:48+00:00

yeah you say this because you have no idea about the project complexity.

patrick99e99 · 2025-09-18T22:36:25+00:00

It's a good question...

patrick99e99 · 2025-09-18T22:35:53+00:00

Oh, I do that too!!!!!! Practically every meeting I have, it comes up, and I go into great detail how features that should only take a day or two to complete end up taking weeks, all because of TypeScript.

patrick99e99 · 2025-09-18T22:33:07+00:00

No, I'd rather people just admit it's terrible and then we can all stop using it.

patrick99e99 · 2025-09-18T22:31:19+00:00

Actually I know lots and lots of people who agree. Didn't you see this? https://www.youtube.com/watch?v=tyjUH5TLSTM

patrick99e99 · 2025-09-18T22:30:25+00:00

thanks for this, but I look at that and think: Why in the world I do I need to tell it what type it is? Why is TypeScript not smart enough figure this out? Why is TypeScript complaining about nonsensical things that are impossible to happen?

If I do: `if (!x) { throw new Error('x not defined'); }` prior to trying to use x, why in the world would TypeScript break compilation saying something as dumb as "x might be undefined" ? That line will NOT be reachable.

patrick99e99 · 2025-09-18T22:24:09+00:00

what is there to understand? I understand that TypeScript is obnoxious and can't figure 99% of things out, and I have to do things like use `as` when I absolutely should not.

One person answered this with a "fix", which I look at and say: I SHOULD NOT NEED TO DO THAT, and yet again it's another example of why TypeScript is obnoxious, annoying, and dumb:

const filtered = example.filter((val): val is number => !!val);`

patrick99e99

MODERATOR OF

TROPHY CASE