mvallebr

4 ms·

1. 1.▲
   by mvallebr 2mo ago

   I am SO impressed by this model! It's cheap as deepseek v4 flash, better than minimax m3 I would say, and almost a glm 5.2. 120b params only for such a good result, with 258k context. This is amazing. Yesterday I was making experiments
2. 2.▲
   by mvallebr 8y ago

   This is reaching state of art status. I always wondered what was the best way of dealing with such conflicts - this is awesome.
3. 3.▲
   by mvallebr 11y ago

   This sounds like awesome news! - How it compares to Cassandra regarding latency? - How is the client API? Does it support lock free communication? Can you send things to nodes in batches?
4. 4.▲
   by mvallebr 14y ago

   I hope FS grows up more and more. I think the future of outsourcing should go this way. Good luck to you guys
5. 5.▲
   by mvallebr 14y ago

   Please, could you share the uses you thoughts for it? This is what we are most interested in. We did the platform for ourselves, and it seems powerful now, we would like to know what could interest others...
6. 6.▲
   by mvallebr 14y ago

   Scheduling is done by any external tool like cron, a java app running quartz or control-m. However, the processor job knows the last time it was run and know which data it should process to update the time. You might also choose to run the
7. 7.▲
   by mvallebr 14y ago

   This is interesting, indeed. As your platform is agnostic to the runtime, wouldn't it be easy to use ours instead of hadoop or storm? Or you don't see any benefit? About the tuples, you still could use them, if I understood it well...