While fiddeling around with mod_fcgid it turned out I have no clue what the settings mean. And they aren’t very good described. Well maybe they are and I’m just not fit enough to get the correct definitions. So I asked Sven…
In my last blog-entry you’ve seen that I compared regexp vs nonregexp-techniques and the result was, that there are „bad“ and „good“ regexp; while the good regexp are as fast as non-regexp-techniques. Let’s take a closer look at what „good“ regexp are. Please notice that I’m not a regexp-magician so if you know about a regexp which would do better than the regexp I’ll show, please let me know.
Yesterday I was talking with Sven about my Imap-Class and I told him that I switched regexp to non-regexp to gain performance. He was asking me whether the use of str* is really faster than the use of regexp in PHP and thus he said „you could write an entry about that in your blog, I’d be interested“ – Hey Sven, here you go.
looking for useful documentation about netboot in Linux is quite difficult nowadays; of the various guides I found on the net only 1 was useful (1 of 30) … No wonder that I came to the conclusion to write my own one…
The goal is, to have a central fileserver which does nfs+dhcp+tftp to make netbooting installation images possible. That’s because I’m usually missing a install CD and I’ve got no spare recordables lying around -> all of my boxes can do netbooting, though.
In my last blog I wrote about optimizing the boot-times using runit and a special kernel. As of today I switched to systemd in Lunar Linux and I’m using connman for networking; Let’s take a look at the boot-times again…
some time ago I wrote a small document about MySQL’s COALESCE usage. Today I was asked to help with such a construct for a similar usage-scenario. Here’s the result:
Currently I’m working on some sort of shipping-system for a customer. It turned out that i was spending 3 days looking for a problem with my query while there was no problem. Well, apart from phpmyadmin 🙂 But, lemme tell you later about it.
I have a few boxes around at home, so if i do video-editing i’d like to benefit from that. We can use some avisynth plugins/enhancements to do so. There are two things we might do: a) running filters in parallel b) handing filters to another box (networking). The problem with multiple cores in Linux is that it’s not easily possible to run Avisynth on many cores in fact it’s per default just running on one core.
There was an entry about vswap in the OpenVZ blogs and i love that new feature. So i decided to build my own kernel in debian with those patches to get that functionality. Continue to read if you’re interested in VSWAP and how to setup your kernel to make use of it.
Since I’m working with avisynth I’ve always been impressed about people who came up with convolution stuff, many numbers and I had no idea what they mean. Reading the help pages on avisynth.org didn’t help – For all people who wanted to know how that works, here’s a little guide (thanks to Kuukunen for explaining)