]]>
]]>
Web app developers spend most of our time not thinking about how data is actually transmitted through the bowels of the network stack. Abstractions at the application layer let us pretend that networks read and write whole messages as smooth streams of bytes. Generally this is a good thing. But knowing what's going underneath is crucial to performance tuning and application design. The character of our users' internet connections is changing and some of the rules of thumb we rely on may need to be revised.
]]>
Reportage is a radically different native Twitter client for your iPhone that provides a radio tuning environment into your Twitter social network. Reportage views a Twitter user as a broadcaster and each user's tweets as a specific broadcast. Similar to a real radio tuner, Reportage allows you to selectively tune into each broadcaster and visualize the conversation.
]]>
]]>
Zemanta is a text enrichment tool. Packaged as a firefox extension, it helps adding tags, photos, links to the texts you type in your web browser. It is based on "natural language processing, machine learning and fine tuning", and would take profit out of SemWeb technologies.
]]>
]]>
]]>
]]>
"Why is IE still relevant and why is it worth spending money on rendering engines when there are open source ones available that can respond to changes in Web standards faster?"
"That's cheeky, but a good question, but cheeky," Ballmer said.
Indeed it is. If I was a Microsoft share holder I would want to know why Microsoft is sinking so much money into its own Web browser rendering engine when there are others available for free.
Normalement, à cet instant on arrête de lire l'article vu la puissance de l'analyse. Et pourquoi Opera dépense tant d'argent alors que Internet Explorer est gratuit ? Et pourquoi la Fondation Mozilla dépense tant d'argent alors que Safari est gratuit ? Et pourquoi Apple dépense tant d'argent alors que le tuning est gratuit ? (ha, on m'informe que le tuning n'est pas gratuit, juste le chromage).
Et d'autre part, si "s'adapter plus vite aux standards" ça veut dire implémenter des bouts d'un machin qui ne sera pas près avant 2012 (oui, je parle de HTML5, qui est parti pour être le plus gros gloubi-boulga depuis VB5 + ActiveX), et pas finir d'implémenter les standards existant ?
When tuning a site's performance, a system administrator needs certain tools to measure and monitor how the site is doing under increasing load, as well as identify where bottlenecks may be. Linux system performance monitoring tools On Linux, there are several tools available to you to do this. We describe what we have found as the most helpful in this section.
Apache prefork, StartServers, MaxSpareServers and MinSpareServers In the most common case, you will be using Apache in the prefork mode, meaning one process per connection, with a pool of processes pre-forked to standby for connections. The number of spare processes is defined by the values MaxSpareServers, MinSpareServers, while the number to start is defined by StartServers.
Out of the box, Zimbra is tuned for a fairly beefy machine. Zimbra will easily consume 1.5GB of ram with default settings. Some of these changes mean turning off a few Zimbra features and there are quite a few ways to do this, so you will need to evaluate memory usage given your own situation. If you simply can't live without *all* the Zimbra features or intend to support a larger (> 15) number of users, my only suggestion is to get more ram ;). But if you are willing to make some compromises, please read on. The changes below are ones that I found to be a reasonable compromise. With a few easy changes, you can bring the memory consumption way down, so that it will hum along just fine on a server with ~512MB of ram. Of course this reduces the amount of users that your server can support, but I've found that for a small installation of around 15 users, these settings will work just fine and give you the same performance as the out-of-the-box config with gobs of RAM. The server I have been testing with has 560MB of ram, and after tuning consumes all the ram and only about 80MB of swap on average. You will find that if you don't make changes similar to the ones suggested below with ~512MB of ram, your Zimbra install will slowly creep up its consumption of swap and your Zimbra install will start to crawl. Also, > 512MB seems to be about the minimum amount of ram to get a useful/zippy server
]]>A systems administrator always needs to be cognizant of system performance. This article drills down into the many aspects of tuning AIX to run Oracle. We'll look at the Virtual Memory Manager (VMM), CPU, Memory, and I/O (disk and network).
Opcode caches save energy, expenses, improve overall user experience on web sites, and it's often one of the simplest optimizations to implement. This article will explain the basics of installing, configuring, and tuning an opcode cache for PHP, the Alternative PHP Cache (APC).
]]>
]]>
Pylot is a free open source tool for testing performance and scalability of web services. It runs HTTP load tests, which are useful for capacity planning, benchmarking, analysis, and system tuning.
]]>