FFmpeg does not write to a specific log file, but rather sends its output to standard error. To capture that, you need to either capture and parse it as it is generated redirect standard error to a file and read that afterward the process is finished Example for std error redirection: ffmpeg -i myinput.avi {a-bunch-of-important-params} … Read more
For very small numbers of sockets (varies depending on your hardware, of course, but we’re talking about something on the order of 10 or fewer), select can beat epoll in memory usage and runtime speed. Of course, for such small numbers of sockets, both mechanisms are so fast that you don’t really care about this … Read more
The speed degradation is to be expected as the number of files being accessed simultaneously increases. Hard disk drives do not like to be accessed in parallel: every time the read/write head needs to switch cylinders you lose several milliseconds. Even if two files are on the same cylinder, or even the same track, you … Read more
This is going to be a bunch of small points. There is sadly no single answer to your question, however. MongoDB allows the OS kernel to handle memory-management. Aside from throwing as much RAM as possible at the problem, there are only a few things that can be done to ‘actively manage’ your Working Set. … Read more
Provided you have a distro that supports the dir_index capability then you can easily have 200,000 files in a single directory. I’d keep it at about 25,000 though, just to be safe. Without dir_index, try to keep it at 5,000.
Disk & RAM Capacity Planning Planning disk and memory capacity for a database server is a black art. More is better. Faster is better. As general guidelines I offer the following: You want more disk space than you’ll EVER need. Take your best estimate of how much disk space you’ll need for the next 3-5 … Read more
vSphere’s memory management is pretty decent, though the terms used often cause a lot of confusion. In general, memory over-commit should be avoided as it creates exactly this type of problem. However, there are times when it cannot be avoided, so forewarned is forearmed! What are the downsides of overcommitting and over-configuring resources (specifically RAM) … Read more
This is true, and it was one of the key motivation to backing the switch from SLC (fast and durable flash cells, but small capacity) to MLC (slower and less durable flash cells, but bigger capacity). To give you some ballpark numbers (on old 34nm tech): SLC drive: 100K P/E cycles (program-erase cycles), 100 GB … Read more
The short answer is: Nobody can answer this question except you. The long answer is that benchmarking your specific workload is something that you need to undertake yourself, because it’s a bit like asking “How long is a piece of string?”. A simple one-page static website could be hosted on a Pentium Pro 150 and … Read more
The Server Fault community generally can’t help you with capacity planning – the best answer we can offer is “Benchmark your code on hardware similar to what you’ll be using in production, identify any bottlenecks, then determine how much of a workload your current hardware can handle, and/or how much hardware horsepower you need to … Read more