FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2329577775> ?p ?o ?g. }

• W2329577775 abstract "Performance test data should be analyzed to determine if performance requirements are being met, to see if they reveal opportunities for performance improvement, and to see if they show signs of lurking performance issues or malfunctions. Automated analyses of the measurements can be useful when the number of resource usage measures and performance measures is large, when the number of nodes under test is large, or when the number of test cases is large. We shall examine this for cases in which the system under test is subjected to a constant load, as might be the case for an online transaction processing system, and for the case where the load is inherently bursty, as would be the case for an alarm or monitoring system that is receiving streams of notifications from many sensors at once. We expect a well behaved system under constant load to reach steady state shortly after the test load begins, and to ramp down to its previous state once the load is withdrawn. This corresponds to a system reaching equilibrium in stochastic terms. We also expect a well behaved system to return to steady state after a surge of traffic abates. Failure to achieve equilibrium under constant load is a sign of a problem that should be investigated. Automated analysis of voluminous test data facilitates the identification of intervals of steady operation and cases when steady operation has not occurred during performance tests. An embedded control or monitoring system, such as a building security system, might be subject to a sustained burst of message traffic in an emergency situation. Fire alarm systems might have to respond to at least one of these messages within seconds of the onset of the burst by triggering bells and sirens, closing doors, and automatically alerting emergency services. They might consist of only a few hosts. An automated tool could use statistical methods to identify phases of execution during an emergency by noting when each thread's processor consumption changes. This facilitates the identification of areas for performance improvement, especially if the system is implemented with so many processes or threads that visual identification of heavy consumers of processing power is difficult. We shall elaborate on these issues in this talk, and also discuss methods for performing automated analyses of load tests of systems whose loads are expected to be steady and of systems whose loads are expected to be intense for a transient period." @default.
• W2329577775 created "2016-06-24" @default.
• W2329577775 creator A5050481496 @default.
• W2329577775 date "2016-03-12" @default.
• W2329577775 modified "2023-09-23" @default.
• W2329577775 title "Automated Analysis of Load Test Results of Systems with Equilibrium or Transient Behavior" @default.
• W2329577775 cites W10077787 @default.
• W2329577775 cites W2097821140 @default.
• W2329577775 doi "https://doi.org/10.1145/2859889.2880447" @default.
• W2329577775 hasPublicationYear "2016" @default.
• W2329577775 type Work @default.
• W2329577775 sameAs 2329577775 @default.
• W2329577775 citedByCount "0" @default.
• W2329577775 crossrefType "proceedings-article" @default.
• W2329577775 hasAuthorship W2329577775A5050481496 @default.
• W2329577775 hasConcept C111919701 @default.
• W2329577775 hasConcept C119599485 @default.
• W2329577775 hasConcept C127313418 @default.
• W2329577775 hasConcept C127413603 @default.
• W2329577775 hasConcept C151730666 @default.
• W2329577775 hasConcept C2777267654 @default.
• W2329577775 hasConcept C2780799671 @default.
• W2329577775 hasConcept C2989121073 @default.
• W2329577775 hasConcept C41008148 @default.
• W2329577775 hasConcept C85761212 @default.
• W2329577775 hasConceptScore W2329577775C111919701 @default.
• W2329577775 hasConceptScore W2329577775C119599485 @default.
• W2329577775 hasConceptScore W2329577775C127313418 @default.
• W2329577775 hasConceptScore W2329577775C127413603 @default.
• W2329577775 hasConceptScore W2329577775C151730666 @default.
• W2329577775 hasConceptScore W2329577775C2777267654 @default.
• W2329577775 hasConceptScore W2329577775C2780799671 @default.
• W2329577775 hasConceptScore W2329577775C2989121073 @default.
• W2329577775 hasConceptScore W2329577775C41008148 @default.
• W2329577775 hasConceptScore W2329577775C85761212 @default.
• W2329577775 hasLocation W23295777751 @default.
• W2329577775 hasOpenAccess W2329577775 @default.
• W2329577775 hasPrimaryLocation W23295777751 @default.
• W2329577775 hasRelatedWork W1577327694 @default.
• W2329577775 hasRelatedWork W2016851290 @default.
• W2329577775 hasRelatedWork W2333401791 @default.
• W2329577775 hasRelatedWork W2377879397 @default.
• W2329577775 hasRelatedWork W2985292772 @default.
• W2329577775 hasRelatedWork W3036918837 @default.
• W2329577775 hasRelatedWork W3038854759 @default.
• W2329577775 hasRelatedWork W4241580893 @default.
• W2329577775 hasRelatedWork W4312097531 @default.
• W2329577775 hasRelatedWork W2758798772 @default.
• W2329577775 isParatext "false" @default.
• W2329577775 isRetracted "false" @default.
• W2329577775 magId "2329577775" @default.
• W2329577775 workType "article" @default.