Article
Version 1
Preserved in Portico This version is not peer-reviewed
Evolving System Bottlenecks in the as a Service Cloud
Version 1
: Received: 9 November 2018 / Approved: 12 November 2018 / Online: 12 November 2018 (08:49:16 CET)
How to cite: D'Souza, S.C. Evolving System Bottlenecks in the as a Service Cloud. Preprints 2018, 2018110270. https://doi.org/10.20944/preprints201811.0270.v1 D'Souza, S.C. Evolving System Bottlenecks in the as a Service Cloud. Preprints 2018, 2018110270. https://doi.org/10.20944/preprints201811.0270.v1
Abstract
The web ecosystem is rapidly evolving with changing business and functional models. Cloud platforms are available in a SaaS, PaaS and IaaS model designed around commoditized Linux based servers. 10 billion users will be online and accessing the web and its various content. The industry has seen a convergence around IP based technology. Additionally, Linux based designs allow for a system wide profiling of application characteristics. The customer is an OEM who provides Linux based servers for telecom solutions. The end customer will develop business applications on the server. Customers are interested in a latency profiling mechanism which helps them to understand how the application behaves at run time. The latency profiler is supposed to find the code path which makes an application block on I/O, and other synchronization primitives. This will allow the customer to understand the performance bottleneck and tune the system and application parameters.
Keywords
cloud systems; AI; cognitive; programming languages; algorithms
Subject
Computer Science and Mathematics, Computer Science
Copyright: This is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
Comments (0)
We encourage comments and feedback from a broad range of readers. See criteria for comments and our Diversity statement.
Leave a public commentSend a private comment to the author(s)
* All users must log in before leaving a comment
