so I did a search for anyone doing microsolder repairs nearby, picked the closest, and found someone who diagnosed, quoted, and then replaced both ports, and a chip that had vaporised itself along the way, for a couple hundred AUD.
27 karma · joined October 4, 2018
so I did a search for anyone doing microsolder repairs nearby, picked the closest, and found someone who diagnosed, quoted, and then replaced both ports, and a chip that had vaporised itself along the way, for a couple hundred AUD.
I don't see a way out of it until either generated content is either completely unable to be distinguished from authored content (unlikely?), or there's a silver bullet for identifying generated content (also unlikely?)
but for caching, all you are doing is leaving off a fraction of the most recent assistant message generation, which will have little/no impact on cache hit rate.
a simple alternative approach is to introduce hysteresis by having both a high and low context limit. if you hit the higher limit, trim to the lower. this batches together the cache misses.
if users are able to edit, remove or re-generate earlier messages, you can further improve on that by keeping track of cache prefixes and their TTLs, so rather than blindly trimming to the lower limit, you instead trim to the longest active cache prefix. only if there are none, do you trim to the lower limit.
if call #1 is the file, call #2 is the file + the question, call #3 is the file + a different question, then yes.
and consider that "the file" can equally be a lengthy chat history, especially after the cache TTL has elapsed.
for example if a user sends a large number of tokens, like a file, and a question, and then they change the question.
see https://gery.casiez.net/1euro/ with plenty of existing implementations to pick from
... has either language leveraged these to better tell the CPU what to do? presumably for perf.
and so I've been a little disappointed with how these devices keep getting bigger and bigger. I was pretty happy with the size of the Pixel 3
I think I like to be able to access the whole screen comfortably with one hand, not fumbling it about. easy to manipulate, easy to pocket. the Pixel 8 shrunk a bit over its predecessors so I nabbed that, and it's probably at or just over the limit for me, size wise
it's more useful to consider what people suggest for a track.
- "you're going to need a diff lock"
- "you're going to need high clearance"
As an aside, if I remember correctly you can also run git without any server at all with multiple contributors. But it isn't the most ergonomic!