<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://epickrram.blogspot.co.uk/2014/05/performance-testing-at-lmax-part-one.html"/>
	<rdf:li rdf:resource="http://www.bloombergview.com/articles/2015-04-02/tesla-stockholders-can-t-take-a-joke"/>
	<rdf:li rdf:resource="http://www.nanex.net/aqck2/4661.html"/>
	<rdf:li rdf:resource="http://pythonsweetness.tumblr.com/post/64740079543/how-to-lose-172-222-a-second-for-45-minutes"/>
	<rdf:li rdf:resource="http://queue.acm.org/detail.cfm?id=2534976"/>
	<rdf:li rdf:resource="http://low-latency.com/article/groundbreaking-results-high-performance-trading-fpga-and-x86-technologies"/>
	<rdf:li rdf:resource="http://www.nanex.net/aqck2/4306.html"/>
	<rdf:li rdf:resource="http://www.economist.com/node/21547988"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work"/>
	<rdf:li rdf:resource="http://www.cnbc.com/id/39664612"/>
	<rdf:li rdf:resource="http://www.nytimes.com/2010/10/02/business/02flash.html?_r=1&amp;src=mv"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://epickrram.blogspot.co.uk/2014/05/performance-testing-at-lmax-part-one.html">
    <title>Performance Testing at LMAX</title>
    <dc:date>2015-06-03T12:49:58+00:00</dc:date>
    <link>http://epickrram.blogspot.co.uk/2014/05/performance-testing-at-lmax-part-one.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Good series of blog posts on the LMAX trading platform's performance testing strategy -- they capture live traffic off the wire, then build statistical models simulating its features.  See also http://epickrram.blogspot.co.uk/2014/07/performance-testing-at-lmax-part-two.html and http://epickrram.blogspot.co.uk/2014/08/performance-testing-at-lmax-part-three.html .]]></description>
<dc:subject>performance testing tests simulation latency lmax trading sniffing packet-capture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c962c123de77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tests"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:simulation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lmax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sniffing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:packet-capture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bloombergview.com/articles/2015-04-02/tesla-stockholders-can-t-take-a-joke">
    <title>SEC vs April Fool's Day</title>
    <dc:date>2015-04-06T20:29:22+00:00</dc:date>
    <link>http://www.bloombergview.com/articles/2015-04-02/tesla-stockholders-can-t-take-a-joke</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>I think that materiality means what it says, and if people or algorithms do dumb things with trivial information that's their problem. But markets are a lot faster and more literal than they were when the materiality standard was created, and I wonder whether regulators or courts will one day decide that materiality is too reasonable a standard for modern markets. The materiality standard depends on the reasonable investor, and in many important contexts the reasonable investor has been replaced by a computer. </blockquote>

]]></description>
<dc:subject>algorithms trading stock stock-market sec materiality april-fools-day tesla investing jokes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:f96edf4070bb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stock"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stock-market"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:materiality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:april-fools-day"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tesla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:investing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jokes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nanex.net/aqck2/4661.html">
    <title>Nanex: &quot;The stock market is rigged&quot; [by HFTs]</title>
    <dc:date>2014-07-16T13:14:04+00:00</dc:date>
    <link>http://www.nanex.net/aqck2/4661.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>All this evidence points to one inescapable conclusion: the order cancellations and trade executions just before, and during the trader's order were not a coincidence. This is premeditated, programmed theft, plain and simple. Michael Lewis probably said it best when he told 60 Minutes that the stock market is rigged.</blockquote>

Nanex have had enough, basically. Mad stuff.]]></description>
<dc:subject>hft stocks finance market trading nanex 60-minutes michael-lewis scams sec regulation low-latency exploits hacks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8f00f85dfa2a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:finance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:market"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nanex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:60-minutes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:michael-lewis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:regulation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:exploits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hacks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pythonsweetness.tumblr.com/post/64740079543/how-to-lose-172-222-a-second-for-45-minutes">
    <title>How to lose $172,222 a second for 45 minutes</title>
    <dc:date>2013-10-22T12:27:50+00:00</dc:date>
    <link>http://pythonsweetness.tumblr.com/post/64740079543/how-to-lose-172-222-a-second-for-45-minutes</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Major outage and $465m of trading loss, caused by staggeringly inept software management: 8 years of incremental bitrot, technical debt, and failure to have correct processes to engage an ops team in incident response.  Hopefully this will serve as a lesson that software is more than just coding, at least to one industry]]></description>
<dc:subject>trading programming coding software inept fail bitrot tech-debt ops incident-response</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:35b102c3a492/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:inept"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bitrot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tech-debt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:incident-response"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://queue.acm.org/detail.cfm?id=2534976">
    <title>Online Algorithms in High-frequency Trading - ACM Queue</title>
    <dc:date>2013-10-19T20:38:52+00:00</dc:date>
    <link>http://queue.acm.org/detail.cfm?id=2534976</link>
    <dc:creator>jm</dc:creator><description><![CDATA[one-pass algorithms for computing mean, variance, and linear regression, from the HFT world.]]></description>
<dc:subject>linear-regression variance mean variability volatility stream-processing online algorithms hft trading</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a346d6588063/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linear-regression"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:variance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mean"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:variability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:volatility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stream-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:online"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://low-latency.com/article/groundbreaking-results-high-performance-trading-fpga-and-x86-technologies">
    <title>Groundbreaking Results for High Performance Trading with FPGA and x86 Technologies</title>
    <dc:date>2013-10-02T12:54:33+00:00</dc:date>
    <link>http://low-latency.com/article/groundbreaking-results-high-performance-trading-fpga-and-x86-technologies</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>The enhancement in performance was achieved by providing a fast-path where trades are executed directly by the FPGA under the control of trigger rules processed by the x86 based functions. The latency is reduced further by two additional techniques in the FPGA – inline parsing and pre-emption.  As market data enters the switch, the Ethernet frame is parsed serially as bits arrive, allowing partial information to be extracted and matched before the whole frame has been received. Then, instead of waiting until the end of a potential triggering input packet, pre-emption is used to start sending the overhead part of a response which contains the Ethernet, IP, TCP and FIX headers. This allows completion of an outgoing order almost immediately after the end of the triggering market feed packet.</blockquote>

Insane stuff. (Via Martin Thompson)]]></description>
<dc:subject>via:martin-thompson insane speed low-latency fpga fast-path trading stock-markets performance optimization ethernet</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:e1e6cba06648/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:martin-thompson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:insane"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:speed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fpga"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fast-path"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stock-markets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ethernet"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nanex.net/aqck2/4306.html">
    <title>Low-latency stock trading &quot;jumps the gun&quot; due to default NTP configuration settings</title>
    <dc:date>2013-06-05T20:40:42+00:00</dc:date>
    <link>http://www.nanex.net/aqck2/4306.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>On June 3, 2013, trading in SPY exploded at 09:59:59.985, which is 15 milliseconds before the ISM's Manufacturing number released at 10:00:00. Activity in the eMini (traded in Chicago), exploded at 09:59:59.992, which is 8 milliseconds before the news release, but 7 milliseconds after SPY.  Note how SPY and the eMini traded within a millisecond for the Consumer Confidence release last week, but the eMini lagged SPY by about 7 milliseconds for the ISM Manufacturing release. The simultaneous trading on Consumer Confidence is because that number is released at the same time in both NYC and Chicago. 

The ISM Manufacturing number is probably released on a low latency feed in NYC, and then takes 5-7 milliseconds, due to the speed of light, to reach Chicago. Either the clock used to release the ISM number was 15 milliseconds fast, or someone (correctly) jumped the gun.

Update: [...] The clock used to release the ISM was indeed, 15 milliseconds fast. This could be from using the default setting of many NTP clients, which allows the clock to drift up to about 16 milliseconds before adjusting time.</blockquote>

]]></description>
<dc:subject>ntp time synchronization spy trading stocks low-latency clocks internet</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c36c7599b498/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ntp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:synchronization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.economist.com/node/21547988">
    <title>High-frequency trading: The fast and the furious | The Economist</title>
    <dc:date>2012-08-03T15:34:00+00:00</dc:date>
    <link>http://www.economist.com/node/21547988</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>
"The NYMEX panel found that Infinium had finished writing the algorithm only the day before it introduced it to the market, and had tested it for only a couple of hours in a simulated trading environment to see how it would perform. The firm's normal testing processes take six to eight weeks. When the algorithm started its frenetic buying spree, the measures designed to shut it down automatically did not work. One was supposed to turn the system off if a maximum order size was breached, but because the machine was placing lots of small orders rather than a single big one the shutdown was not triggered. The other measure was meant to prevent Infinium from selling or buying more than a certain number of contracts, but because of an error in the way the rogue algorithm had been written, this, too, failed to spot a problem."
<blockquote>]]></description>
<dc:subject>hft automation trading markets stocks nymex bugs software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:647442de3e15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:markets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nymex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bugs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work">
    <title>How does LMAX's disruptor pattern work? - Stack Overflow</title>
    <dc:date>2011-11-23T09:52:35+00:00</dc:date>
    <link>http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work</link>
    <dc:creator>jm</dc:creator><description><![CDATA[LMAX's "Disruptor" concurrent-server pattern, claiming to be a higher-throughput, lower-latency, and lock-free alternative to the SEDA pattern using a massive ring buffer.  Good discussion here at SO.  (via Filippo)]]></description>
<dc:subject>via:filippo servers seda queueing concurrency disruptor patterns latency trading performance ring-buffers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:388ee9929e15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:filippo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:seda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queueing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disruptor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ring-buffers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cnbc.com/id/39664612">
    <title>Flash Crash - Norwegians Convicted for Outwitting 'Trading Robots' - CNBC</title>
    <dc:date>2010-10-14T21:51:38+00:00</dc:date>
    <link>http://www.cnbc.com/id/39664612</link>
    <dc:creator>jm</dc:creator><description><![CDATA['The two men worked out how the computerized system would react to certain trading patterns – allowing them to influence the price of low-volume stocks.'  Yet another risk of automated traders]]></description>
<dc:subject>trading stocks automated-trading flash-crash high-frequency-trading</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:e34401bd3a37/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automated-trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flash-crash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:high-frequency-trading"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nytimes.com/2010/10/02/business/02flash.html?_r=1&amp;src=mv">
    <title>Lone Sale of $4.1 Billion in Contracts Led to ‘Flash Crash’ in May</title>
    <dc:date>2010-10-04T11:32:46+00:00</dc:date>
    <link>http://www.nytimes.com/2010/10/02/business/02flash.html?_r=1&amp;src=mv</link>
    <dc:creator>jm</dc:creator><description><![CDATA['as the computers of the high-frequency traders traded contracts back and forth, a “hot potato” effect was created, the report said, as contracts changed hands 27,000 times in 14 seconds, but with eventually only 200 actually being bought or sold.'  upshot: horrifically complex distributed feedback loops now directly impact our economies -- great :(]]></description>
<dc:subject>distributed-systems distcomp flash-crash stock-market trading automation via:nelson sec nyse high-frequency-trading</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:b5c59d9d74e1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distributed-systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distcomp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flash-crash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stock-market"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:nelson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nyse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:high-frequency-trading"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>