nivekkevin

Idea: can the agents make faces? 1. Programmatically--agents see each other's faces, and they can make their own. They can choose to ignore, but at least make that an input to the decision making. 2. Display them in UI--I just want to see their faces instead next to their model code names :)

what's generally the go-to these days for non server-less?

"Loved by Teams Worldwide"

searched three names, cannot find any match

The issue I have with these wrapper services is privacy.

> We collect several types of information from and about users of our Services:

> ...

> Prompts and Queries: The text prompts and questions you submit to AI models

if it is live, oh man they better have a good moderation system

p99 for the same reason has been used widely in monitoring systems and benchmarks.

it does feel like so, the position eventually loses its meaning as more and more data gets crunched by the training process, eventually it's just a context of the past 4 tokens it feels like

it's a rolling buffer, so it just upsert index % 4 in this case

The annoying (?) part of Scala Spark is the lack of notebook ecosystem. Also spark-submit requires a compiled jar for Scala yet only the main python script for Python. I would've loved Scala Spark if the eco system was in place.

Why does this look extremely sketchy?

One significant disadvantage of PySpark is its reliance on py4j to serialize and deserialize objects between Java and Python when using Python UDFs. This constant overhead can become burdensome as data volume increases in such an exchange. However, I am glad to see efforts to create a data pipeline framework using Python and Ray.

~One suggestion, a Scala/Java Spark run of those benchmarks should be a valid baseline to compare against as well instead of PySpark.~ Ah it's SparkSQL so the execution probably wouldn't have much of py4j involvement, except for the collect.