Srinath Shankar
Microsoft
30 Papers
306 Citations
Srinath Shankar is an academic researcher from Microsoft. The author has contributed to research in topics: Graph (abstract data type) & Query optimization. The author has an hindex of 14, co-authored 30 publications. Previous affiliations of Srinath Shankar include LinkedIn & University of Wisconsin-Madison.
Chat about Author
Papers
Towards Multi-tenant Performance SLOs
Willis Lang,Srinath Shankar,Jignesh M. Patel,Ajay Kalhan +3 more
- 01 Apr 2012
TL;DR: This paper presents a framework that takes as input the tenant workloads, their performance SLOs, and the server hardware that is available to the DaaS provider, and outputs a cost-effective recipe that specifies how much hardware to provision and how to schedule the tenants on each hardware resource.
Wimpy node clusters: what about non-wimpy workloads?
Willis Lang,Jignesh M. Patel,Srinath Shankar +2 more
- 07 Jun 2010
TL;DR: Results show that in most cases, computationally complex queries exhibit disproportionate scaleup characteristics which potentially makes scale-out with low-end nodes an expensive and lower performance solution.
Patent
Optimizing queries of parallel databases
Eric R. Robinson,Alan Halverson,Rimma V. Nehme,Srinath Shankar +3 more
- 23 Oct 2012
TL;DR: In this article, a parallel-aware optimizer can parallelize the logical serial plan search space by augmenting the data structure (e.g., transforming the SQL Server MEMO into a parallel MEMO).
26
Patent
Translating queries into graph queries using primitives
Srinath Shankar,Huaxin Liu,Robert W. Stephenson,Scott M. Meyer +3 more
- 17 Feb 2016
TL;DR: In this paper, a system may translate a query associated with a type of database (such as a relational database) into the query, and then the system may execute the query against the graph database and may receive a result that includes a subset of the graph.
24
Towards Multi-Tenant Performance SLOs
TL;DR: This paper presents a framework that takes as input the tenant workloads, their performance SLOs, and the server hardware that is available to the DaaS provider, and outputs a cost-effective recipe that specifies how much hardware to provision and how to schedule the tenants on each hardware resource.
23