Sstomach Virus 6 Weeks

Optimize the Post Title in Real Time Search Google Blogger

It is very important to have a site "seo friendly" as well as a blog.
The first think we learn about the SEO is the funcion of the meta tags, in particular of the title, and the importance to have the relevant keywords at the beginning of our tags.

By default Blogger put the name of our blog before the post title but we can in any moment change and optimize it; infact we can decide to have the post title before our blog name or only the post title alone.

If you want now to change it you have to open your blog setting click on Layout and select Edit HTML .
Than you have to search for the meta title default:

<title><data:blog.pageTitle/></title>

and modify it with one of the two below.

If you want to have the post title before your blog name

<b:if cond='data:blog.pageType == "item"'>
<title><data:blog.pageName/> - <data:blog.title/></title>
<b:else/>
<title><data:blog.pageTitle/></title>
</b:if>

In this case you can also reach a "branding goal" cause your blog name will appear in the search results.

If you want a title composed only by the post title alone :

<title><data:blog.pageName/></title>
<b:else/>
<title><data:blog.pageTitle/></title>
</b:if>

Now you can save the setting and visulize your blog.

Naughty Birthday Cake Ideas

Google launched today the Real Time Search : since few hours, after our search, we can see a list of live updates from Twitter, FriendFeed but also blog posts and news articles.

The results appears in the first page in a specific space; for example you can find below my Google page after the query "Google real time search".


Click on "Latest results for.." or select "Lastest" from the menu options if you want to visualize only real time updates for your search.
For example, I inserted the keyword "Google" and below my results: a list of tweets, post and news just published.


Obviously this page is update in real time so if you search for a very generic subject you may have a too frenetic page result; for that reason, in every moment you can stop and resume the update.

About the partners Google announced, besides Twitter and FriendFeed also Facebook , Jaiku , Identi.ca e Myspace .

It is intresting and cute also the video explaining the new real time search in a simple and prompt way:

Jon Cryer Per Episode

Google and searches in real time

Google annuncia oggi il lancio del Real Time Search : da poche ore è infatti possibile visualizzare, a seguito di una ricerca, gli aggiornamenti pubblicati utenti ad esempio su Twitter e FriendFeed ma anche su blog e siti di notizie.

The results are incorporated into the first page in a window dedicated to updates automatically, for example here is the first page after I search for "real time Google search":


It 'still can refine your search only to "real time results by selecting from the side menu item" Latest ".
For example, I have searched "Google" and here my results will be a list of tweets, titles of posts and announcements have been published:


course page, automatically in real time, it may be, especially for some very general search like mine, a little too frantic.
For this reason, you can stop at any time and return the results to be updated.

Speaking of partners, as well Twitter and FriendFeed , have also been announced Facebook , Jaiku, Identi.ca and Myspace who posted the ad on his blog .

is definitely worth a watch this video about the news in a simple and direct:

Rolling A Neckerchief

A question I have always done, when I'm working with a ext2 / 3 again on larger and larger volumes, is how can a file system virtually unchanged for decades in support of hundreds of GB logical drives without some as "feeling the pinch." For this reason I prefer filesystem più moderni ma, ahimè, non supportati o non mainstream sotto Linux.

ext3 per altro verso presenta caratteristiche molto interessanti per Oracle: supporta il direct I/O e l'I/O asincrono, due feature molto importanti per massimizzare le prestazioni di un database sotto Linux. Ma i 4 KB di dimensione massima del blocco e la struttura abbastanza tradizionale del filesystem mi lasciano perplesso di fronte a unità logiche di qualche terabyte.
Pensiamo ad esempio ai nuovi filesystem come btrfs o ZFS (due a caso :-)). Praticamente non c'è paragone tra ext3 e i filesystem di nuova generazione.

Mentre aspettiamo che Linux si decida ad adottare un filesystem di livello enterprise e con caratteristiche modern, at least we can maximize the performance of ext3 adapting the underlying hardware abstraction with which we operate, typically drive RAID.

We must consider that some RAID levels such as RAID5, suffer delays in writing because of the structural calculation of a tie, arriving at peak performance when you make a writing a full stripe. When creating a RAID volume, you can usually specify the stripe size from a few KB to about 256 KB or more.

ext3 has a couple of parameters that help to optimize the file for writing: stride and stripe-width .

stride is the number of filesystem blocks that are used to write a stripe (in the case of ext3 block is almost always 4 KB).
stripe-width is the amount of blocks that are used to cover a complete writing on all disks that "carry" data, multiple of the stride.
Let me explain with an example: RAID5 uses a distributed parity resulting in a space of n-1 disks, and then with a certain stripe size will be written n-1 stripe that "bring data" disks and a parity stripe and this is the stripe width, and ext3 is measured in blocks and corresponds to stride * (n-1) * blocksize in the case of RAID5. There is a

document Centos ext3 optimization with optimization for RAID in the last paragraph, even if there is any error notation. The fact that stripe-width has been removed from CentOS 5.3 is true, unfortunately for RHEL. I can not explain this fact, when on my Ubuntu desktop is present.

Someone has also created a special calculator that can be found here: ~ http://busybox.net/ aldot / mkfs_stride.html