{"action":"opened","issue":{"url":"https://api.github.com/repos/andresvivancov/BDAPRO-WindowsBenchmarking/issues/15","repository_url":"https://api.github.com/repos/andresvivancov/BDAPRO-WindowsBenchmarking","labels_url":"https://api.github.com/repos/andresvivancov/BDAPRO-WindowsBenchmarking/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/andresvivancov/BDAPRO-WindowsBenchmarking/issues/15/comments","events_url":"https://api.github.com/repos/andresvivancov/BDAPRO-WindowsBenchmarking/issues/15/events","html_url":"https://github.com/andresvivancov/BDAPRO-WindowsBenchmarking/issues/15","id":197070064,"number":15,"title":"Meeting Dec 14 on 9.30 AM Wednesday. ","user":{"login":"andresvivancov","id":15791882,"avatar_url":"https://avatars.githubusercontent.com/u/15791882?v=3","gravatar_id":"","url":"https://api.github.com/users/andresvivancov","html_url":"https://github.com/andresvivancov","followers_url":"https://api.github.com/users/andresvivancov/followers","following_url":"https://api.github.com/users/andresvivancov/following{/other_user}","gists_url":"https://api.github.com/users/andresvivancov/gists{/gist_id}","starred_url":"https://api.github.com/users/andresvivancov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andresvivancov/subscriptions","organizations_url":"https://api.github.com/users/andresvivancov/orgs","repos_url":"https://api.github.com/users/andresvivancov/repos","events_url":"https://api.github.com/users/andresvivancov/events{/privacy}","received_events_url":"https://api.github.com/users/andresvivancov/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-22T00:57:19Z","updated_at":"2016-12-22T00:57:19Z","closed_at":null,"body":"- Analyze Yahoo streaming benchmarks (from their blog probably)\r\n\r\nGoal: Measure the latency of the frameworks under low throughput scenarios\r\nSolution:\r\n Flink and Storm are good (law latency) and good throughput\r\nSpark high latency(bad) and acceptable throughput\r\nFlink did not use checkpoint to guarantee processing\r\n\r\n- Read the blog post of Data Artizans about yahoo benchmarks (http://data-artisans.com/extending-the-yahoo-streaming-benchmark/)\r\n\r\nGoal: measure the maximum throughput of each system while maintaining the best possible fault tolerance.\r\nGoal 2: Do some optimizations and variants such as not use key store REDIS\r\n\r\n- What are the differences?\r\n\r\n![image](https://cloud.githubusercontent.com/assets/15791882/21411545/8feb2db8-c7e9-11e6-8e4c-bb62effcd194.png)\r\n\r\n\r\nWith the new approach \r\n\r\nFlink is more efficient because can manage more throughput\r\n\r\nFault tolerant and consistency in Flink and Storm\r\n\r\n![image](https://cloud.githubusercontent.com/assets/15791882/21411562/b8c07c8e-c7e9-11e6-8cca-e115f6069a6f.png)\r\n\r\n![image](https://cloud.githubusercontent.com/assets/15791882/21411572/c05d1ae2-c7e9-11e6-923d-a98357692f00.png)\r\n\r\n\r\n- What are the bottlenecks in yahoo streaming benchmarks?\r\n\r\n\r\nRedis\r\n\r\nStoring Key Value Store, while updating the windows very quickly , crash in 280,000 events/sec\r\n\r\n\r\n\r\n- Depending on bottlenecks, state the clear definition of the problem.\r\n\r\n\r\nDelete Key Value Store, beacuase the is part of the fault tolerant local state (with the checkpoints??), \r\nWith thise approach pass from 280,000 events/sec  to 15,000,000 events/sec\r\n"}}
{"actor":{"display_login":"andresvivancov"}}