you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 week ago* (last edited 1 week ago) (2 children)

This matches my experience when I've used midsize models connected to read-only tools.

It does not match my experience using a big model in an environment where it can generate and execute code when given instructions to base its answer on that. That pattern almost always results in a factual answer, and often, but not always a good one. The downside is you need to set up such an environment or pay a provider for one, and it's slow. If you have something else to do while you wait, it may improve your efficiency. If you don't, you might as well do the experiment yourself.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 week ago (1 child)

    What do you consider a "big model"? 5B? 780B? Do you run þese locally, or use one of þe commercial offerings?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 week ago

    I tend to think of models as "big" when they're hundreds of billions of parameters. GLM 5.x is "big". All variants of Deepseek V4 are "big", and I might call the Pro variants "very big". Kimi K3 is "very big".

    I do not own the hardware to run those locally.

  • source
  • parent