161–170 of 236 posts
Earlier quoted context omitted.
Out of curiosity what does the industry best practice dictates between webm and mp4 for this kind of stuff? - Which one is more accessible? - Which one is more "compressed" and mobile ready?
Chromium browsers compiled without proprietary codecs require webm. It's a small subset of people (I am one), but I just don't play and/or leave sites with mp4 only.
Am I the only one having problems to follow .gif "demos"? When I get to the image, it is in the middle of everything and I don't really have an idea what is going on. Even watching it multiple times, I am not sure where it starts, ends, what the individual steps are. Or is it because I just don't know enough about this stuff?
Oh, and to make this more than a simple rant/whine, some constructive suggestions that could possibly solve the problem: - Normal video with playback controls? - Add a clearly distinguishable "this is where it starts" screen. - Is there maybe a way to control playback of a gif via JS/HTML? Add a "restart" button. - Add a timeline into the .gif that shows where I am (similar to usual video player).
Awesome! While I was at AWS Summit in NY, I asked a round circle of AWS ECS/EKS users (Container orchestration products) about thoughts on a Docker container service that could execute like a FaaS product and there seemed to be none anyone knew of. I have a portion of a legacy application that's used infrequently and too costly to decompose but works fine Dockerized. Looking forward to using your product!
1. AWS Fargate
2. Joyent Triton (which was as simple as DOCKER_HOST= docker run back in 2015)
3. hyper.sh (available since 2016 I think?)
4. OpenFaaS cloud (though you have to go through a couple more steps, you can bring a custom docker image as your 'function').
5. A metric ton of hosted kubernetes offerings
Earlier quoted context omitted.
You need both formats, mp4 for ios and webm for android Not sure this is "standard" but imgur has their gifv "format" which will serve up the correct underlying format to the device https://help.imgur.com/hc/en-us/articles/208606616-What-is-G...
why both? Android can do mp4, no?
Earlier quoted context omitted.
Can your workers run Docker containers?
Workers don't run Docker containers intentionally. The goal with Workers is to run with a lower memory overhead (~3 MB) and lower startup time (~5 ms) than you can get with full container isolation. This allows your Worker to run affordably in 150+ locations around the world. In many ways it's the ultimate destination for serverless, running code in a multitenant process where all you manage is your code.
Awesome! While I was at AWS Summit in NY, I asked a round circle of AWS ECS/EKS users (Container orchestration products) about thoughts on a Docker container service that could execute like a FaaS product and there seemed to be none anyone knew of. I have a portion of a legacy application that's used infrequently and too costly to decompose but works fine Dockerized. Looking forward to using your product!
I'm amazed no one knew of one. Off the top of my head, services which let you run docker containers without dealing with any servers yourself: 1. AWS Fargate 2. Joyent Triton (which was as simple as DOCKER_HOST= docker run back in 2015) 3. hyper.sh (available since 2016 I think?) 4. OpenFaaS cloud (though you have to go through a couple more steps, you can bring a custom docker image as your 'function'). 5. A metric…
So this is different from running docker containers on heroku because heroku has 1 to n autoscaling but not 0 to n? What are the other fundamental differences?
It's actually pretty similar to the Heroku free tier dyno "sleep" till there's a trigger, but it's stateless. Different pricing, different ways of conceptualizing but from a user perspective that's a pretty good comparison.
Earlier quoted context omitted.
Setting up and maintaining a kubernetes cluster on my own would probably kill me desire to touch a computer again. Azure and Google provides free Kubernetes-cluster-management-as-service. But you are right, its still a hassle.
Been going through that process the past few days on Scaleway, as they don't have a hosted K8. It's... tough... but I'm learning a lot and have a much deeper understanding of K8s clusters from an operational perspective now. I have a much deeper understanding of the magic happening behind the scenes to keep everything talking to each other, and even if I wind up on a hosted solution in the end, it's been invaluable.
So I've been messing with Fn + Clojure + Graal Native Image and I'm seeing cold start times around 300-400ms and hot runs around 10-30ms. TLS adds something like 100-150ms on top of that. I was excited about seeing improved docker start times, but it seems like you guys are pretty much at the same place I am with it. Here's my question, being relatively ignorant of Docker's internals: _is it possible_ to improve that…
I take the view that there is a "warmth hierarchy" (an idea I spitballed with other folks in Knative before Matt Moore took it and filled it out a lot).
You have a request or message. You need to process it. The hierarchy runs CPU > Memory > Disk > Cold.
CPU-warm: immediately schedulable by the OS. Order of nanoseconds.
Memory-warm: in-memory but can't be immediately scheduled. Our reference case is processes that have been cgroup frozen. Order of tens of milliseconds.
Disk-warm: the necessary layers are all present on the node which is assigned to launch the process. Order of hundreds of milliseconds.
Cold start: nothing is present on the node which is assigned to launch the process. It will need to fetch some or all layers from a registry. Order of seconds to minutes.
Some of these problems can't be solved by Kubernetes (it doesn't know how to freeze a process), some of them can't be solved by Docker (it doesn't know about other nodes that might have warmer disk caches). Then there's the business of deciding where to route traffic, how to prewarm caches and based on what predictive approach, avoiding siloisation of processes due to feedback loops.
As these are knocked down they will pay dividends for everyone.
> “A very common category of failure of software applications is associated with failures that occur after programs get into states that the developers didn't anticipate, usually arising after many cycles. In other words, programs can fail unexpectedly from accumulating state over a long lifespan of operation. Perhaps the most common example of this is a memory leak: the unanticipated growth of irreclaimable memory t…
Really brings to mind that Rasmus Lerdorf quote: > I'm not a real programmer. I throw together things until it works then I move on. The real programmers will say "Yeah it works but you're leaking memory everywhere. Perhaps we should fix that." I’ll just restart Apache every 10 requests.