An unofficial blog that watches Google's attempts to move your operating system online since 2005. Not affiliated with Google.

Send your tips to gostips@gmail.com .

July 4, 2006

Google Shows Debug Parameters

Someone at DigitalPoint forum has found a mysterious data dump in the Google cache of a page. You can see a lot of interesting parameters and values about the processing time, latency, number of queries, supplemental results. We can think at the server-side Google like a command-line utility that has adjustable parameters (resolve unreachable server, use the new anti-spam algorithm, don't use the new PageRank called IndyRank). Google has a debugging version of the client interface that probably came up by accident:

pacemaker-alarm-delay-in-ms-overall-sum 2341989
pacemaker-alarm-delay-in-ms-total-count 7776761
cpu-utilization 1.28
cpu-speed 2800000000
timedout-queries_total 14227
num-docinfo_total 10680907
avg-latency-ms_total 3545152552
num-docinfo_total 10680907
num-docinfo-disk_total 2200918
queries_total 1229799558
e_supplemental=150000
–pagerank_cutoff_decrease_per_round=100
–pagerank_cutoff_increase_per_round=500
–parents=12,13,14,15,16,17,18,19,20,21,22,23
–pass_country_to_leaves –phil_max_doc_activation=0.5
–port_base=32311 –production –rewrite_noncompositional_compounds –rpc_resolve_unreachable_servers –scale_prvec4_to_prvec –sections_to_retrieve=body+url+compactanchors –servlets=ascorer –supplemental_tier_section=body+url+compactanchors –threaded_logging –nouse_compressed_urls –use_domain_match –nouse_experimental_indyrank –use_experimental_spamscore –use_gwd
–use_query_classifier –use_spamscore –using_borg

This blog is not affiliated with Google.