![]() I don’t know if I haven’t found the right brand, but it seems that most leader hoses or hose reels I’ve seen, tried, or read about are built as cheaply as possible and seemingly designed to spring a leak after just one season. The leader hose that came with my hose reel – that’s a different story. We replaced older outdoors spigots with new frost-free ones, and the threads are a dream. ![]() We have to do it empirically, which is fundamentally on par with println debugging.Threaded garden hose connections can be a test of one’s patience. The only one I really know of is service retirement (replace 2-3 services with 2 new, refactored services), and we don't have static analysis tools that can tell us deterministically when we can remove an API. However there's a conspicuous lack of tools and techniques to make that practical. CI/CD argues that if something is difficult we should do it all the time so that it's routine (or stop doing it entirely). If you stick this problem in front of the CI/CD mirror, it's painful to face. With monolithic systems we see this late in the lifecycle in the form of Conway's Law. Of course then you have to take your knowledge out of the 'lab' and apply it in vivo.Ī lot of our (and in particular, my) best features come from of relocating the boundaries between things, to make space for features that weren't considered in the original design. Small projects tend not to have that problem and so make a better petri dish. Relentless Refactoring is a great tool, but one that is often stymied by faddish behaviors like micro-services/modules. It's of course not visible light, but satellite communication also uses radio waves normally, which are not visible light either.įinally, either through cables or through satellite communication, the distance/c minimum theoretical one-way latency is usually a significant under-estimation of the actually possible minimal latency, since the straight-line distance is significantly shorter than the actual cable/satellite-and-back distance that the signals must travel - the difference in straight-line VS physical path distance is typically much larger than the difference between the theoretical speed of light and the actual speed of the electrical signal propagation. That is, they directly transmit light through the cable.įourth, it should be noted that electricity is actually the same thing as light, since photons are the carrier particles of the electric field (when two charged particles interact, they are actually exchanging a photon). Third of all, intercontinental cables are normally fiber optic, for several reasons. Second of all, electrical signals in cables move at speeds slightly lower than c, but very close to it, so the speed of light is still a very good approximation of the possible upper bound. Some of the same principles can be applied even for servers that render dynamically (by caching expensive fragments).įirst of all, the "speed of light" is usually referring to c, the maximum speed that matter or energy can move at. Of that, ~140ms is connection setup (DNS, TCP, TLS). The images bring the total time up to around 5.7s.Īs a point of comparison, my site (nginx serving static content, on the 0.25 CPU GCP instance) serves the index page in 250ms. ![]() I'm not sure how the implementation works internally but that seems like a long time for a site served from memory and aiming to be "high-performance". There may be further opportunities for improvement.Ĭhrome and Curl both report it takes about 1100ms to load the linked page's HTML, split about 50/50 between establishing a connection and fetching content.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |