Performance counter markdown docs

Doc/Readme.md

@@ -5,9 +5,9 @@
 In the LINQPad experience of Tx is **as if all the events were in a Database**
 Except, no database is involved - the the query happens directly on raw logs/traces or real-time sessions 
 
-- [Getting started](https://tx.codeplex.com/wikipage?title=LINQPad%20Driver) with the Tx LINQPad Driver
-- [Queries on trace from HTTP.sys](https://tx.codeplex.com/wikipage?title=HTTP%20Samples)  - the kernel driver used by IIS (Internet Information Services)
-- [Average and Deviation](https://tx.codeplex.com/wikipage?title=Performance%20Counter%20Samples). This query is based on .blg file (the default output of PerfMon for counters)
+- [Getting started](../Source/Tx.Linqpad/Readme.md) with the Tx LINQPad Driver
+- [Queries on trace from HTTP.sys](../Samples/LinqPad/Queries/HTTP.sys/Readme.md)  - the kernel driver used by IIS (Internet Information Services)
+- [Average and Deviation](..\Samples\LinqPad\Queries\Performance Counters\Readme.md). This query is based on .blg file (the default output of PerfMon for counters)
 - [Cross /provider & cross machine queries](https://tx.codeplex.com/wikipage?title=IE_IIS). Response time of IE on client machine and IIS on server.
 
 ## Using Tx from C# code

Samples/LinqPad/Queries/Performance Counters/Readme.md

@@ -0,0 +1,34 @@
+# Performance Counter Samples
+
+For these samples we will illustrate opening .blg (binary log file), which was created from PerfMon.
+
+Binary log is the default format for performance counter recording, and has two advantages compared to .csv (comma separated) and .tsv (tab-separated) files:
+* When tracing to .csv instances (e.g. Processes) are enumerated once. New instances that appear during the recording are not picked up
+* the binary files are more compact when the trace is huge
+
+Here is what this .blg file looks in PerfMon:
+
+![PerfCtr_PerfMon.JPG](PerfCtr_PerfMon.JPG)
+
+Now we are going to access the same data with LINQPad queries, directly from the .blg file.
+
+## Raw Data
+
+When connecting to .blg files, you don't need to worry about Manifests (the .blg format contains the metadata). This shows as tree on the left. Hover with the mouse to see the occurrence count and further details.
+
+Then, the following query shows the raw data for the CPU:
+
+![PerfCtr_1_RawData.JPG](PerfCtr_1_RawData.JPG)
+
+## Average and Deviation
+
+Frequently, we want to smoothen the trend of performance counters, but not lose the information about the level of noise. Here is a query that computes both the average and the standard deviation:
+
+![PerfCtr_2_AverageAndDeviation.JPG](PerfCtr_2_AverageAndDeviation.JPG)
+
+The output of this query looks like this:
+
+![PerfCtr_2_AverageAndDeviation_Output.JPG](PerfCtr_2_AverageAndDeviation_Output.JPG)
+
+
+