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…
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?
I hope FS grows up more and more. I think the future of outsourcing should go this way. Good luck to you guys
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…
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…
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…
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?
I hope FS grows up more and more. I think the future of outsourcing should go this way. Good luck to you guys
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…
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…