Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jimmyl02
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
jimmyl02
1y ago
I think there is no way to tell and we can only see with more research and time. One nuanced part that might not be clear is the transformer was a huge part of what made traditional LLMs scale. With the diffusion transformer and newer archi
32.
▲
by
jimmyl02
1y ago
cool initiative! building apps locally without the cloud services has definitely been quite challenging both to setup and maintain when I've done it before
33.
▲
by
jimmyl02
2y ago
the most unintuitive part is that from my understanding, individual tokens are routed to different experts. this is hard to comprehend with "experts" as that means two you can have different experts for two sequential tokens right
34.
▲
by
jimmyl02
2y ago
the large context windows generally involve RoPE[0] which is a trick that allows the training window to be smaller but expand larger during inference. it seems like they have a new "iRoPE" which might have better performance? [0]
35.
▲
by
jimmyl02
2y ago
the needle in a haystack benchmark looks good but at this point I think we need new benchmarks to test actual understanding of content in such a large window.
36.
▲
by
jimmyl02
2y ago
I feel like understanding this difference is what a good product manager should be responsible for. Not just optimizing any metric that is available but understanding the meaning behind them and choosing the push them the right direction.
37.
▲
Warning Do not try building bitdrift at home
(blog.bitdrift.io)
2 points
by
jimmyl02
2y ago
|
0 comments
38.
▲
by
jimmyl02
2y ago
I wonder at which scale spark fits into this picture and what the tradeoffs / benefits would be
39.
▲
by
jimmyl02
2y ago
pretty cool and thanks for the details about TUN devices! I believe wireguard runs over UDP and while you still need a TUN device, it has kernel implementations to handle encrypting the traffic.
40.
▲
Advancements in Embedding-Based Retrieval at Pinterest Homefeed
(medium.com)
1 points
by
jimmyl02
2y ago
|
0 comments
41.
▲
by
jimmyl02
2y ago
Based on the status report, it seems like it was related to a database disaster and mention recovering shards. Publicly they say they are using vitess[0] so I wonder if there was some issues there. I wonder if there will be a more detailed
42.
▲
by
jimmyl02
2y ago
don't most architectures resolve this via superscaling / some up scaling pipeline after that adds the details? iirc stable diffusion xl uses a "refiner" after initial generation
43.
▲
by
jimmyl02
2y ago
one small idea I read somewhere that I found interesting for thought at a startup: you might work on an entire page that impacts thousands of people at a larger firm: you might work on a single form that impacts millions
44.
▲
by
jimmyl02
2y ago
wouldn't it be coredns caches the information and records from API server for X amount of time (it seems like this might be 20 minutes?) then once the 20 minutes expired coredns would query api server, receive no response, then fail? I
45.
▲
by
jimmyl02
2y ago
splitting the control and data plane is a great way to improve resilience and prevent everything from being hard down. I wonder how it could be accomplished with service discovery / routing. maybe instead of relying on kubernetes DNS f
46.
▲
by
jimmyl02
2y ago
pretty new to the large scale data processing space so not sure if this is a known question but isn't the purpose of spark that it can be distributed across many workers and parallelized? I guess the scale of data here ~100GB is manage
47.
▲
Luma Photon and Photon Flash
(renewed-companies-663689.framer.app)
4 points
by
jimmyl02
2y ago
|
0 comments
48.
▲
by
jimmyl02
2y ago
this is a really neat writeup! the design choice to make each "exit node" control the local wireguard connections instead of a global control plane is pretty neat. an unfinished project I worked on ( https://github.com&#
49.
▲
by
jimmyl02
2y ago
I think a good way of looking at it is risk. Is the change (whether it is code or configuration, etc.) worth the risk it brings on. For example if it's a small feature then it probably makes sense to wait and keep things stable. But, i
50.
▲
Uv: An Fast Python Package Manager [video]
(youtube.com)
1 points
by
jimmyl02
2y ago
|
1 comments
51.
▲
by
jimmyl02
2y ago
One thing I appreciate very much about this article is that they describe things they tried and didn't work as well. It's becoming increasingly rare (and understandably why) for articles to describe failed attempts but it's v
52.
▲
Pinterest Tiered Storage for Apache Kafka: A Broker-Decoupled Approach
(medium.com)
2 points
by
jimmyl02
2y ago
|
1 comments
53.
▲
SpaceX Falcon 9 suffers rare failure on orbit during Starlink deployment
(techcrunch.com)
1 points
by
jimmyl02
2y ago
|
0 comments
54.
▲
by
jimmyl02
2y ago
the view I now have is that for a relational table, yes you have to suffer through migrations but at least they are in sql. for document based stores, you still have to have migrations, but they are just implemented in code json documents s
55.
▲
by
jimmyl02
2y ago
I don't know if the tone selector UX was used by other companies before but it is so simple and intuitive I'm surprised I haven't seen it more. I wouldn't be shocked if it becomes a standard within all the AI tools Great
56.
▲
by
jimmyl02
2y ago
curious what are the performance characteristics here? I would assume something like Nginx that has been optimized over a longer period of time / a more specific use case would have non-negligible performance benefits at scale?
57.
▲
by
jimmyl02
3y ago
From what I know about RWKV, it's mostly a one man effort and doesn't have the same data pipeline / resources as most major labs. It's a bit unfortunate but I'm curious about the performance given the same training
58.
▲
by
jimmyl02
3y ago
curious to hear does anyone know what the mentioned alternatives are? a super simple to use wireguard control plane is super valuable and PiVPN seemed to fit that gap perfectly unfortunate that it's come to an end but it's nice to
59.
▲
by
jimmyl02
3y ago
on the fault tolerance side - if it's really this fast why not just store the data in a high-availability database / data lake then run batch processing? it doesn't seem like this use case requires real-time indexing and sear
60.
▲
by
jimmyl02
3y ago
modern mitigations have made exploits much more difficult, however researchers continue to find bypasses to these mitigations. there are "classic" techniques to bypass most of the modern protections and if there isn't then re
More ›