<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><style><!--
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:-536869121 1107305727 33554432 0 415 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-536859905 -1073732485 9 0 511 0;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;}
a:link, span.MsoHyperlink
{mso-style-noshow:yes;
mso-style-priority:99;
color:#0563C1;
mso-themecolor:hyperlink;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-noshow:yes;
mso-style-priority:99;
color:#954F72;
mso-themecolor:followedhyperlink;
text-decoration:underline;
text-underline:single;}
span.EmailStyle17
{mso-style-type:personal-compose;
mso-style-noshow:yes;
mso-style-unhide:no;
mso-ansi-font-size:11.0pt;
mso-bidi-font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
color:windowtext;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.WordSection1
{page:WordSection1;}
--></style></div><div data-marker="__QUOTED_TEXT__"><div class="WordSection1"><p class="MsoNormal"><a name="_MailOriginal">CS Department Colloquium Speaker</a></p><span style="mso-bookmark:_MailOriginal"></span><p class="MsoNormal">Jose Faleiro from Yale University</p><p class="MsoNormal">Monday, April 9, 2018 - 12:30pm</p><p class="MsoNormal">Computer Science - Room 105</p><p class="MsoNormal">Host: Wyatt Lloyd</p><p class="MsoNormal"> </p><p class="MsoNormal">"High Performance Serializable Transactions via Deterministic Execution"</p><p class="MsoNormal"> </p><p class="MsoNormal">Abstract: </p><p class="MsoNormal">Concurrency, the processing of multiple requests simultaneously, is one of the most challenging problems large-scale server applications face in practice. Accordingly, database systems research has long made the case for automatically handling concurrency in the database by guaranteeing <span class="SpellE">serializability</span>. <span class="SpellE">Serializability</span> shields applications from reasoning about concurrency, and allows developers to focus entirely on implementing application logic. Unfortunately, in the 40-plus years since its inception, <span class="SpellE">serializability</span> has not seen wide adoption in practice. This is because weaker guarantees, which expose applications to concurrency and the inevitable bugs that arise, perform significantly better.</p><p class="MsoNormal"> </p><p class="MsoNormal">In this talk, I will discuss my research on addressing the performance limitations of <span class="SpellE">serializability</span> via deterministic transaction execution. Deterministic transaction execution exploits the fact that a large class of modern server applications do not require the full generality of conventional database transactions. By tailoring transaction execution mechanisms for this class of applications, my research shows that it is possible to achieve <span class="SpellE">serializability</span> with minimal performance overhead. I will first describe a serializable multi-versioning mechanism that decouples conflicting reads and writes, and subsequently outperforms a state-of-the-art implementation of the weaker guarantee of snapshot isolation by over 3x. Next, I will describe piecewise visibility, a concurrency control mechanism that isolates requests at a finer granularity than entire transactions, which consequently permits aggressive serializable transaction <span class="SpellE">interleavings</span> and outperforms the weaker guarantee of read committed by over 3x. Finally, I will discuss ongoing work that applies deterministic transaction execution principles to address replication lag in Facebook’s production MySQL infrastructure.</p><p class="MsoNormal"> </p><p class="MsoNormal">Bio: </p><p class="MsoNormal">Jose Faleiro is a PhD candidate in computer science at Yale University. His research interests are in data management systems, multi-core systems, and distributed systems. His thesis research investigates the use of deterministic execution to enable scalable and efficient transaction processing on main-memory multi-core database systems. In addition to his academic research at Yale, Jose has worked on large-scale real world systems, including Microsoft’s Orleans cloud programming framework, and Facebook’s production MySQL infrastructure. He is the recipient of the Alan J. Perlis Fellowship at Yale, and a Microsoft Research Tech Transfer Award. He has an undergraduate degree in computer science from the Birla Institute of Technology and Science (BITS), <span class="SpellE">Pilani</span>, <span class="SpellE">India.a</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;mso-fareast-font-family:"Times New Roman""></span></p></div><br></div></div></body></html>