Live data from Hacker News

Our new search index: Caffeine

googleblog.blogspot.com

51–60 of 82 posts

Re: Our new search index: Caffeine

#54

old index: problem: parts of the index were refreshed at a faster rate than others; the main layer would update every couple of weeks and to refresh a layer of the old index, Google would analyze the entire web first. impact: there was a significant delay between when Google found a page and made it available to its users. new index: solution: caffeine, Google's new index will analyze the web in small portions and up…

Hmmm... come to think about it I have been getting quite a lot of results from CodeWeblog.com in my search results. Unfortunately, that site seems to be a link farm and its so useless that I reported it to the Google spam page. Maybe its appearance in the top sites was a result of the Caffeine changes.

Re: Our new search index: Caffeine

#55

Earlier quoted context omitted.

Well, the serving part of their index is in memory (or largely so) as has been publicly announced. But are you really suggesting they might do the same for indexing? Let's suppose for a second that they can get 8GB sticks of RAM for 1/3 the retail price of around $600, and for the sake of the back of the envelope calculation, let's round it up to ten GB. So let's call it $20/GB of RAM. Four gigabyte sticks might seem…

Why use RAM? You can get a 500GB SSD for $1000. 100 PB would cost you $200 Million, which is peanuts to Google. Or you could use PCIe SSD drives. You can get a TB of PCIe for $3000, and a 5 PCIe x16 mother board at Fry's costs around $300. You could get 100PB of PCIe SSd storage for around $300 M. You could use RAM for very fast cache, and SSD storage for faster than HDD indexing and retrieval.

Ssds aren't reliable enough for Google scale. The rater number of writes before failure for Flash would make replacement a constant effort for them and ruin any economy. You need Ram for the reliability as well as the random access speed.

Re: Our new search index: Caffeine

#56
What I dislike about Google's current algorithm is that when I search for a common term such as "javadoc simpledateformat", the API documentation for Java 1.4.2 (as opposed to 1.6) comes up as apparently, that is what most documents on the web link to. I hope this new index will allow more recent and more up-to-date documents to get to the top of the results list.

Re: Our new search index: Caffeine

#58
post #56

What I dislike about Google's current algorithm is that when I search for a common term such as "javadoc simpledateformat", the API documentation for Java 1.4.2 (as opposed to 1.6) comes up as apparently, that is what most documents on the web link to. I hope this new index will allow more recent and more up-to-date documents to get to the top of the results list.

I tend to use "java6 simpledateformat" as my query for that.

Re: Our new search index: Caffeine

#60
post #2

Wow is that ever a terrible infographic.

I'd have to disagree. It shows us that Google has adopted the experimental "Bohr" model of database indexing.

I'm not sure if I get this...is this just a pithy one-liner, or am I missing something deeper here?
Post reply on HN