Fixing project formatting and a few data bugs
parent
24fd736944
commit
d81eededb7
|
|
@ -6,7 +6,9 @@
|
|||
<div class=links>
|
||||
{{#if github}}<a href="http://github.com/{{github}}">GitHub</a>{{/if}}
|
||||
{{#if twitter}}<a href="http://twitter.com/{{twitter}}">Twitter</a>{{/if}}
|
||||
{{#if scholar}}<a href="https://scholar.google.com/citations?user={{scholar}}">Google Scholar</a>{{/if}}
|
||||
{{#if cv}}<a href="{{cv}}">CV</a>{{/if}}
|
||||
|
||||
</div>
|
||||
{{{contents}}}
|
||||
<h2>Publications</h2>
|
||||
|
|
|
|||
|
|
@ -329,7 +329,7 @@ body {
|
|||
.person .links a {
|
||||
font-size: 12px;
|
||||
color: #041a9b;
|
||||
margin-left: 20px;
|
||||
margin-right: 20px;
|
||||
margin-left: 10px;
|
||||
margin-right: 10px;
|
||||
text-decoration: none;
|
||||
}
|
||||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
github: okennedy
|
||||
twitter: xthemage
|
||||
scholar: 9Q9tiCsAAAAJ
|
||||
cv: http://www.cse.buffalo.edu/~okennedy/okennedy.pdf
|
||||
pic: ../assets/people/oliver.jpg
|
||||
pic_w: 181
|
||||
|
|
|
|||
|
|
@ -1,21 +1,27 @@
|
|||
<h1 style="text-align: justify;"><img class="alignnone wp-image-5" src="http://mjolnir.cse.buffalo.edu/wp-content/uploads/2014/10/ASTral.png" alt="ASTral" width="43" height="43" /> <span style="text-decoration: underline;">ASTral / Just In Time Datastructures</span></h1>
|
||||
<p style="text-align: justify;"><b>Students:</b> Jerry Ajay</p>
|
||||
<p style="text-align: justify;">Recently, a swath of specialized data management systems has attempted to displace traditional relational databsaes, each sacrificing a measure of physical independence for the consequent performance gains. However, relying on an entire data management system built around a specific set of performance/capability tradeoffs requires making strong assumptions about (often unpredictable) workload expectations. ASTral does for specialized databse systems what self-describing data did for specialized schemas. ASTral involves several sub-projects:</p>
|
||||
<img style="float: left" src="{{rootPath}}assets/logos/astral.png" width="86" height="86" />
|
||||
# ASTral
|
||||
|
||||
<h6 style="text-align: justify;">Just-In-Time Data Structures</h6>
|
||||
<p style="text-align: justify;">ASTral is based on an idea called <a href="http://github.com/okennedy/jitd">Just-in-time datastructures</a>, where data structure manipulation and access logic are decoupled from the physical representation. A just-in-time data structure uses a set of simple semantic and structural building blocks both to emulate the behavior of existing data structures, and to dynamically create new data structures synthesized on-the-spot to match presented workloads.</p>
|
||||
__Students:__ {{list projectStudents.astral}}
|
||||
|
||||
<h6 style="text-align: justify;">User-Facing App Benchmarks</h6>
|
||||
<p style="text-align: justify;">User-facing applications regularly encounter some of the most dynamic environments possible, and are an ideal fit for just-in-time data structures and ASTral in general. Understanding these changing workloads is critical, and with that in mind we're partnering with <a href="https://phone-lab.org">PhoneLab</a> to understand how user-facing apps interact with SQL. Using to real-world data gathered from an instrumented version of SQLite, we're developing a benchmark for pocket-scale data management.</p>
|
||||
<p style="text-align: justify;"><i>(The ASTral project is being developed in collaboration with Luke Ziarek, and Geoff Challen)</i></p>
|
||||
Recently, a swath of specialized data management systems has attempted to displace traditional relational databsaes, each sacrificing a measure of physical independence for the consequent performance gains. However, relying on an entire data management system built around a specific set of performance/capability tradeoffs requires making strong assumptions about (often unpredictable) workload expectations. ASTral does for specialized databse systems what self-describing data did for specialized schemas. ASTral involves several sub-projects:
|
||||
|
||||
<h4 style="text-align: justify;">Software</h4>
|
||||
<ul style="text-align: justify;">
|
||||
<li><a href="http://github.com/UBOdin/jitd">Just-In-Time Data Structures</a> (GitHub)</li>
|
||||
</ul>
|
||||
<h4 style="text-align: justify;">Publications</h4>
|
||||
<ul>
|
||||
<li style="text-align: justify;"><a href="http://odin.cse.buffalo.edu/wp-content/uploads/2015/06/2015-TPCTC-SQLite-submitted.pdf">Pocket Data: The need for TPC-MOBILE</a> (TPC-TC 2015)</li>
|
||||
<li style="text-align: justify;"><a href="http://odin.cse.buffalo.edu/wp-content/uploads/2014/11/main.pdf">Just-in-Time Data Structures</a> (CIDR 2015)</li>
|
||||
<li style="text-align: justify;"><a href="http://okennedy.xthemage.net/papers/laasie_webdb2013.pdf">Monadic Logs for Collaborative Web Applications</a> (WebDB 2013)</li>
|
||||
</ul>
|
||||
## Just-In-Time Data Structures
|
||||
|
||||
ASTral is based on an idea called <a href="http://github.com/okennedy/jitd">Just-in-time datastructures</a>, where data structure manipulation and access logic are decoupled from the physical representation. A just-in-time data structure uses a set of simple semantic and structural building blocks both to emulate the behavior of existing data structures, and to dynamically create new data structures synthesized on-the-spot to match presented workloads.
|
||||
|
||||
## User-Facing App Benchmarks
|
||||
User-facing applications regularly encounter some of the most dynamic environments possible, and are an ideal fit for just-in-time data structures and ASTral in general. Understanding these changing workloads is critical, and with that in mind we're partnering with <a href="https://phone-lab.org">PhoneLab</a> to understand how user-facing apps interact with SQL. Using to real-world data gathered from an instrumented version of SQLite, we're developing a benchmark for pocket-scale data management.
|
||||
|
||||
_(The ASTral project is being developed in collaboration with Luke Ziarek, and Geoff Challen)_
|
||||
|
||||
------
|
||||
|
||||
## Software
|
||||
|
||||
* <a href="http://github.com/UBOdin/jitd">Just-In-Time Data Structures</a> (GitHub)
|
||||
|
||||
## Publications
|
||||
|
||||
{{#each projectPubs.astral}}
|
||||
* __{{title}}__ <br/> _{{venue}}_ {{{resourcesFormat}}}
|
||||
{{/each}}
|
||||
|
|
|
|||
|
|
@ -1,10 +1,21 @@
|
|||
<h1><img class="alignnone wp-image-7" src="http://mjolnir.cse.buffalo.edu/wp-content/uploads/2014/10/BlackHat.png" alt="BlackHat" width="52" height="52" /><span style="text-decoration: underline;">Insider Threat Detection</span></h1>
|
||||
<b>Students:</b> Duc Luong, Ting Xie, Gokhan Kul, Patrick Coonan
|
||||
---
|
||||
title: Insider Threats
|
||||
---
|
||||
|
||||
|
||||
<img src="{{rootPath}}assets/logos/BlackHat.png" alt="BlackHat" width="104" height="104" style="float: left"/>
|
||||
# Insider Threat Detection
|
||||
|
||||
__Students:__ {{list projectStudents.insider-threats}}
|
||||
|
||||
One of the greatest threats to a the security of a database system comes from within: Users who have been granted access to data using it in a malicious or illegitimate way. Often this is simply a matter of practicality; It is rarely feasible to establish an access control policy that is sufficiently permissive to be usable, while still being sufficiently restrictive to preclude malicious use. Our goal is to develop new types of statistical signatures for a user or role's behavior as they access a database. Using these signatures, we can identify non-standard behvaior that could be evidence of malicious activity.
|
||||
|
||||
<i>(Insider Threats is supported by NSF Grant #69110 and is in collaboration with Hung Ngo, Shambhu Upadhyay and Varun Chandola, Rick Jesse and Manish Gupta)</i>
|
||||
<h4 style="text-align: justify;">Publications</h4>
|
||||
<ul>
|
||||
<li style="text-align: justify;"><a href="http://odin.cse.buffalo.edu/wp-content/uploads/2015/08/mist04pp.pdf">A Preliminary Cyber Ontology for Insider Threats in the Financial Sector</a> (MIST 2015)</li>
|
||||
</ul>
|
||||
_(Insider Threats is supported by NSF Grant #69110 and is in collaboration with Hung Ngo, Shambhu Upadhyay and Varun Chandola, Rick Jesse and Manish Gupta)_
|
||||
|
||||
------
|
||||
|
||||
## Publications
|
||||
|
||||
{{#each projectPubs.insider-threats}}
|
||||
* __{{title}}__ <br/> _{{venue}}_ {{{resourcesFormat}}}
|
||||
{{/each}}
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Mimir
|
|||
---
|
||||
<img src="../../assets/logos/mimir_logo_final.png" alt="mimir_logo_final" width="539" height="214" />
|
||||
|
||||
__Students:__ Ying Yang, Niccolo Meneghetti, Arindam Nandi, Vinayak Karuppasamy
|
||||
__Students:__ {{list projectStudents.mimir}}
|
||||
|
||||
_(Mimir is supported by gifts from Oracle University Relations, and is being developed in collaboration with Ronny Fehling, Dieter Gawlick, Zhen Hua Liu, Boris Glavic, and Jan Chomicki)_
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,10 @@
|
|||
<img src="../../assets/logos/PocketData.png" alt="PocketData" width="207" height="207" />
|
||||
# Pocket-Scale Data Management
|
||||
---
|
||||
title: PocketData
|
||||
---
|
||||
<img src="../../assets/logos/PocketData.png" alt="PocketData" width="207" height="207" style="float: left"/>
|
||||
# PocketData
|
||||
|
||||
__Students:__ Jerry Ajay
|
||||
__Students:__ {{list projectStudents.pocketdata}}
|
||||
|
||||
The world’s 2 billion smartphones represent the most powerful and pervasive distributed system ever built. Open application marketplaces, such as the Google Play Store, have resulted in a vibrant software ecosystem comprising millions of smartphone and tablet apps in hundreds of different categories that both meet existing user needs and provide exciting novel capabilities. As mobile apps and devices become even more central to the personal computing experience, it is increasingly important to understand and improve their performance. In partnership with <a href="https://phone-lab.org">UB's PhoneLab</a>, we are analyzing SQLite logs from smartphones deployed in the wild.
|
||||
|
||||
|
|
@ -11,9 +14,13 @@ Second, mobile app embedded databases support single apps that may issue queries
|
|||
|
||||
To explore these ideas we are beginning by building a smartphone embedded app database benchmark—actually a benchmark <em>generator</em>, which will be able to use traces of database activity to synthesize a benchmark for any app. This feature is critical to ensure that we can support the variety of app database usage patterns and update the benchmark suite easily as they change. We are also evaluating the performance and energy consumption of SQLite, the embedded database provided by default to Android apps, against alternatives such as <a class="external" href="https://en.wikipedia.org/wiki/Berkeley_DB" target="_blank">BerkeleyDB</a> and <a class="external" href="https://en.wikipedia.org/wiki/H-Store" target="_blank">H-Store</a>.
|
||||
|
||||
---
|
||||
|
||||
## Publications
|
||||
|
||||
* <a href="http://odin.cse.buffalo.edu/wp-content/uploads/2015/06/2015-TPCTC-SQLite-submitted.pdf">Pocket Data: The Need for TPC-MOBILE</a> (TPC-TC 2015)
|
||||
{{#each projectPubs.pocketdata}}
|
||||
* __{{title}}__ <br/> _{{venue}}_ {{{resourcesFormat}}}
|
||||
{{/each}}
|
||||
|
||||
## Resources
|
||||
|
||||
|
|
|
|||
|
|
@ -38,6 +38,9 @@ function plugin() {
|
|||
}).join(" | ")
|
||||
+ ")"
|
||||
)
|
||||
for(i in details.projects){
|
||||
push(studentsByProject, details.projects[i], details.name);
|
||||
}
|
||||
}
|
||||
if(typeof details.link == 'undefined'){
|
||||
details.link = linkName(name)
|
||||
|
|
@ -62,6 +65,8 @@ function plugin() {
|
|||
lab = lab.concat(alumni)
|
||||
|
||||
smith.metadata().labMembers = lab
|
||||
// console.log(studentsByProject)
|
||||
smith.metadata().projectStudents = studentsByProject
|
||||
|
||||
|
||||
done()
|
||||
|
|
|
|||
|
|
@ -81,7 +81,8 @@ function plugin() {
|
|||
|
||||
// Associate the publication with each of its projects
|
||||
for(p in pub.projects){
|
||||
push(pubsByProject, pub.projects[p].replace(/-/g,""), pubMeta)
|
||||
// console.log("Associating "+pubMeta.title+" with "+pub.projects[p])
|
||||
push(pubsByProject, pub.projects[p], pubMeta)
|
||||
}
|
||||
}
|
||||
var out = []
|
||||
|
|
@ -90,6 +91,7 @@ function plugin() {
|
|||
}
|
||||
// console.log(out)
|
||||
smith.metadata()["allpubs"] = out.reverse()
|
||||
// console.log(pubsByProject)
|
||||
smith.metadata()["projectPubs"] = pubsByProject
|
||||
done()
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in New Issue