Compared to cloudflare workers, which has free bandwidth, bunnys bandwidth is not that cheap at 0.01$/GB
So while their example suggests stream-encoding video is possible, it would probably be cost-prohibitive.
3,835 karma · joined October 2, 2013
Compared to cloudflare workers, which has free bandwidth, bunnys bandwidth is not that cheap at 0.01$/GB
So while their example suggests stream-encoding video is possible, it would probably be cost-prohibitive.
Stemming: Reducing words to their base or root form (e.g., “working,” “worked” becoming “work”).
Lemmatization: Similar to stemming, but more sophisticated, accounting for context (e.g., “better” lemmatizes to “good”).
Token normalization: Standardizing tokens, such as converting “wrk” to “work” through predefined rules (case folding, character replacement).
Fuzzy matching: Allowing approximate matches based on edit distance (e.g., “wrk” matches “work” due to minimal character difference).
Phonetic matching: Matching words that sound similar, sometimes used to match abbreviations or common misspellings.
Thesaurus-based search: Using a predefined list of synonyms or alternative spellings to expand search queries.
Most of these are open and free lists you can use, check the sources on manticore search for example.
On KV they expect up to 30 second latency before a write can be written everywhere, I expect similar here.
Which also means it may take 10 seconds before you can (reliably) read the write globally.
I keep failing to see how this can replace regionally placed database clusters which can serve a continent in milliseconds.
Edit: I know it uses streams, but those are only to 5 followers and CF have hundreds of datacenters. There is no physical way to guarantee reads in seconds unless all instances of the SQLite are always connected and even then, packet latency will cause issues.
- Automatic connection pooling
- 400MB/s+ of throughput
- 20 000+ keys and larger values (10-50kb)
- 1000+ concurrent reads/writes
- 200-250MB of RAM usage max
Without breaking a sweat, the limitation was my keydb test server.
https://github.com/Gaulomatic/AirPodsSanity
I didn't create this, but I do detest subscription models on bugfixes..
This would be saturated by a single file download. Hopefully it's only a beta limitation!
https://github.com/01-ai/Yi-Coder/issues/6#issuecomment-2334...
Works very well now! 65K input tokens with 8192 output tokens is no longer an issue on my 4090. (It maxes out on 22GB/VRAM)
Unfortunately, this has always been my experience with all open source code models that can be self-hosted.
https://youtu.be/tIIWYh601tg?si=3azdig7logfSWYKu
Check what this simmer is saying about it, it was an eyeopener for me as well