The Experts below are selected from a list of 84 Experts worldwide ranked by ideXlab platform

Henk Corporaal - One of the best experts on this subject based on the ideXlab platform.

  • the boat hull model adapting the roofline model to enable performance prediction for parallel computing
    ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, 2012
    Co-Authors: Cedric Nugteren, Henk Corporaal
    Abstract:

    Multi-core and many-core were already major trends for the past six years, and are expected to continue for the next decades. With these trends of parallel computing, it becomes increasingly difficult to decide on which architecture to run a given application. In this work, we use an algorithm classification to predict performance prior to algorithm implementation. For this purpose, we modify the roofline model to include class information. In this way, we enable Architectural Choice through performance prediction prior to the development of architecture specific code. The new model, the boat hull model, is demonstrated using a GPU as a target architecture. We show for 6 example algorithms that performance is predicted accurately without requiring code to be available.

  • PPOPP - The boat hull model: adapting the roofline model to enable performance prediction for parallel computing
    Proceedings of the 17th ACM SIGPLAN symposium on Principles and Practice of Parallel Programming - PPoPP '12, 2012
    Co-Authors: Cedric Nugteren, Henk Corporaal
    Abstract:

    Multi-core and many-core were already major trends for the past six years, and are expected to continue for the next decades. With these trends of parallel computing, it becomes increasingly difficult to decide on which architecture to run a given application. In this work, we use an algorithm classification to predict performance prior to algorithm implementation. For this purpose, we modify the roofline model to include class information. In this way, we enable Architectural Choice through performance prediction prior to the development of architecture specific code. The new model, the boat hull model, is demonstrated using a GPU as a target architecture. We show for 6 example algorithms that performance is predicted accurately without requiring code to be available.

Cedric Nugteren - One of the best experts on this subject based on the ideXlab platform.

  • the boat hull model adapting the roofline model to enable performance prediction for parallel computing
    ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, 2012
    Co-Authors: Cedric Nugteren, Henk Corporaal
    Abstract:

    Multi-core and many-core were already major trends for the past six years, and are expected to continue for the next decades. With these trends of parallel computing, it becomes increasingly difficult to decide on which architecture to run a given application. In this work, we use an algorithm classification to predict performance prior to algorithm implementation. For this purpose, we modify the roofline model to include class information. In this way, we enable Architectural Choice through performance prediction prior to the development of architecture specific code. The new model, the boat hull model, is demonstrated using a GPU as a target architecture. We show for 6 example algorithms that performance is predicted accurately without requiring code to be available.

  • PPOPP - The boat hull model: adapting the roofline model to enable performance prediction for parallel computing
    Proceedings of the 17th ACM SIGPLAN symposium on Principles and Practice of Parallel Programming - PPoPP '12, 2012
    Co-Authors: Cedric Nugteren, Henk Corporaal
    Abstract:

    Multi-core and many-core were already major trends for the past six years, and are expected to continue for the next decades. With these trends of parallel computing, it becomes increasingly difficult to decide on which architecture to run a given application. In this work, we use an algorithm classification to predict performance prior to algorithm implementation. For this purpose, we modify the roofline model to include class information. In this way, we enable Architectural Choice through performance prediction prior to the development of architecture specific code. The new model, the boat hull model, is demonstrated using a GPU as a target architecture. We show for 6 example algorithms that performance is predicted accurately without requiring code to be available.

Andy Zaidman - One of the best experts on this subject based on the ideXlab platform.

  • EVOL/IWPSE - Multi-tenant SaaS applications: maintenance dream or nightmare?
    Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE) on - IWPSE, 2010
    Co-Authors: Cor-paul Bezemer, Andy Zaidman
    Abstract:

    Multi-tenancy is a relatively new software architecture principle in the realm of the Software as a Service (SaaS) business model. It allows to make full use of the economy of scale, as multiple customers - "tenants" - share the same application and database instance. All the while, the tenants enjoy a highly configurable application, making it appear that the application is deployed on a dedicated server. The major benefits of multi-tenancy are increased utilization of hardware resources and improved ease of maintenance, in particular on the deployment side. These benefits should result in lower overall application costs, making the technology attractive for service providers targeting small and medium enterprises (SME). However, as this paper advocates, a wrong Architectural Choice might entail that multi-tenancy becomes a maintenance nightmare.

  • multi tenant saas applications maintenance dream or nightmare
    International Workshop on Principles of Software Evolution, 2010
    Co-Authors: Cor-paul Bezemer, Andy Zaidman
    Abstract:

    Multi-tenancy is a relatively new software architecture principle in the realm of the Software as a Service (SaaS) business model. It allows to make full use of the economy of scale, as multiple customers - "tenants" - share the same application and database instance. All the while, the tenants enjoy a highly configurable application, making it appear that the application is deployed on a dedicated server. The major benefits of multi-tenancy are increased utilization of hardware resources and improved ease of maintenance, in particular on the deployment side. These benefits should result in lower overall application costs, making the technology attractive for service providers targeting small and medium enterprises (SME). However, as this paper advocates, a wrong Architectural Choice might entail that multi-tenancy becomes a maintenance nightmare.

Cor-paul Bezemer - One of the best experts on this subject based on the ideXlab platform.

  • EVOL/IWPSE - Multi-tenant SaaS applications: maintenance dream or nightmare?
    Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE) on - IWPSE, 2010
    Co-Authors: Cor-paul Bezemer, Andy Zaidman
    Abstract:

    Multi-tenancy is a relatively new software architecture principle in the realm of the Software as a Service (SaaS) business model. It allows to make full use of the economy of scale, as multiple customers - "tenants" - share the same application and database instance. All the while, the tenants enjoy a highly configurable application, making it appear that the application is deployed on a dedicated server. The major benefits of multi-tenancy are increased utilization of hardware resources and improved ease of maintenance, in particular on the deployment side. These benefits should result in lower overall application costs, making the technology attractive for service providers targeting small and medium enterprises (SME). However, as this paper advocates, a wrong Architectural Choice might entail that multi-tenancy becomes a maintenance nightmare.

  • multi tenant saas applications maintenance dream or nightmare
    International Workshop on Principles of Software Evolution, 2010
    Co-Authors: Cor-paul Bezemer, Andy Zaidman
    Abstract:

    Multi-tenancy is a relatively new software architecture principle in the realm of the Software as a Service (SaaS) business model. It allows to make full use of the economy of scale, as multiple customers - "tenants" - share the same application and database instance. All the while, the tenants enjoy a highly configurable application, making it appear that the application is deployed on a dedicated server. The major benefits of multi-tenancy are increased utilization of hardware resources and improved ease of maintenance, in particular on the deployment side. These benefits should result in lower overall application costs, making the technology attractive for service providers targeting small and medium enterprises (SME). However, as this paper advocates, a wrong Architectural Choice might entail that multi-tenancy becomes a maintenance nightmare.

Damián Serrano - One of the best experts on this subject based on the ideXlab platform.

  • A System of Architectural Patterns for Scalable, Consistent and Highly Available Multi-Tier Service-Oriented Infrastructures
    Architecting Dependable Systems VI, 2009
    Co-Authors: Ricardo Jiménez-peris, Marta Patiño-martínez, Bettina Kemme, Francisco Perez-sorrosal, Damián Serrano
    Abstract:

    Service-oriented architectures have become prevalent in enterprise information systems. The underlying infrastructure is typically architected with multiple tiers in order to separate the different concerns such as interface, business logic and data. Modern information systems have strict availability and scalability requirements. The main technique to attain these properties is replication. However, system architects are confronted with a complex environment in which they have to decide which tier(s) to replicate and how. The Architectural Choice can have great implications for the degree of scalability and availability that can actually be achieved. Furthermore, maintaining consistency is affected by the way the system is replicated. In this chapter, we survey the state of the art in this area and digest it in the form of a system of Architectural patterns that will guide system architects and practitioners in evaluating and selecting the appropriate Architectural Choices to attain a highly available, consistent and scalable service-oriented infrastructure.

  • WADS - A System of Architectural Patterns for Scalable, Consistent and Highly Available Multi-Tier Service-Oriented Infrastructures.
    2008
    Co-Authors: Ricardo Jiménez-peris, Marta Patiño-martínez, Bettina Kemme, Francisco Perez-sorrosal, Damián Serrano
    Abstract:

    Service-oriented architectures have become prevalent in enterprise information systems. The underlying infrastructure is typically architected with multiple tiers in order to separate the different concerns such as interface, business logic and data. Modern information systems have strict availability and scalability requirements. The main technique to attain these properties is replication. However, system architects are confronted with a complex environment in which they have to decide which tier(s) to replicate and how. The Architectural Choice can have great implications for the degree of scalability and availability that can actually be achieved. Furthermore, maintaining consistency is affected by the way the system is replicated. In this chapter, we survey the state of the art in this area and digest it in the form of a system of Architectural patterns that will guide system architects and practitioners in evaluating and selecting the appropriate Architectural Choices to attain a highly available, consistent and scalable service-oriented infrastructure.