Tomorrow is World IPv6 Day and I went ahead and made my blog IPv6 compatible.
There is just one minor annoyance, its not really the Dual-Stack solution everyone is going for, Froxlor does not support IPv4+IPv6 domain names (yet?).
So, for now, you may be able to access this blog on IPv6+IPv4 through blog.ipv6.lifetimeblood.info, but the images, javascripts and links still point to IPv4. Thats a limitation by WordPress and the extension im using, “W3 Total Cache“, but I’m trying to do a work-around.
Long story short: IPv6-only – doesn’t quite work yet, IPv6+v4 is recommended.
I’ve wanted to upgrade from my trusty Phenom 955 to a nice SandyBridge 2600K system for a long time and finally have almost all the funds I need. ![]()
- Intel Core i7-2600K, 4x 3.40GHz – ~255€ (MF)
- ASUS P8Z68-V, Z68 – ~132€ (MF)
- 4GB DDR3-1333 G.SKILL CL9-9-9-24 – 0€ (got it cheap on zack-zack.com earlier this year for this purpose)
This will be one beast of a workstation with the multiplier unlocked and bluetooth on the mainboard. The new graphical UEFI BIOS adds the cherry on top.
I’m excited! ![]()
Update: (24.5.11) Delayed for about 3-4 weeks, the mainboard isn’t available. :[
Update2: (31.5.11) Hardware ordered! Now we play the waiting game. ![]()
Update3: (4.6.11) The waiting game sucks, I wan’t my hardware! ![]()
Update4: (6.6.11) Packet tracking code received, Yay! The Hardware is now 12,03 € cheaper than when I ordered it. FFFFFFFFFFF-
Update5: (7.6.11) Package tracking says it should get delivered today. ![]()
Update6: (7.6.11) Its done!
4 cores + HT = 8 blazing fast cores. Gonna post some pics of the retrofitting later/tomorrow.
I noticed that the Aprilon MineCraftApproval system got slower and slower over time so I whipped up a crude profiling mechanism, extending the mysqli class with microtime() time-tracking code and function call-frequency-tracking code using debug_backtrace().
It also prints out every MySQL query made, the call-stack which led to this query and sorts everything by how long it took for the each transaction.
Bear in mind that this includes processing overhead by the MySQLi PHP extension, libmysql library on the system and sockets opening/closing, receiving and sending if the database is on a remote server.
You can see example output on the right and you may notice a few warnings regarding “No possible_keys”.
That means the query could not use any indices because the table doesn’t have any matching the WHERE clause (cut off on pic.).
The number of warnings shrunk to zero after a few ALTER TABLE, ADD INDEX(..),
and the time to execute the MySQL queries was reduced from 59ms (wolfram: ~blink of an eye) to 16.17ms (wolfram: ~nerve impulse to travel the length of a human).
Excuse my french, but that’s fuckin’ impressive.
Even if’s ‘just’ a difference of 42.84ms, it still makes an impact on the experience of the whole application.
What am I doing?- Nichijou 1. January, 2012
- Mashiroiro Symphony 15. November, 2011
- Yuru Yuri 18. August, 2011
- Hanasaku Iroha 13. July, 2011
Interesting stuff
Archives






