4th International Conference on Principles and Practices ... - MADOC

More documents

Recommendations

Info

[10] N. Gold. Hypothesis-based concept assignment to support software maintenance. In Proceedings of the IEEE <strong>International</strong> <strong>Conference</strong> on Software Maintenance, pages 545–548, 2001. [11] N. Gold, M. Harman, D. Binkley, and R. Hierons. Unifying program slicing and concept assignment for higher-level executable source code extraction. Software—Practice & Experience, 35(10):977–1006, 2005. [12] M. Golm, C. Wawersich, J. Baumann, M. Felser, and J. Kleinöder. Understanding the performance of the Java operating system JX using visualization techniques. In Proceedings of the 2002 joint ACM-ISCOPE conference on Java Grande, page 230, 2002. [13] M. Hauswirth, P. F. Sweeney, A. Diwan, and M. Hind. Vertical profiling: understanding the behavior of object-oriented applications. In Proceedings of the 19th ACM SIGPLAN <strong>Conference</strong> on Object-Oriented Programming, Systems, Languages, and Applications, pages 251–269, 2004. [14] G. Morrisett, D. Walker, K. Crary, and N. Glew. From system F to typed assembly language. ACM Transactions on Programming Languages and Systems, 21(3):527–568, 1999. [15] P. Nagpurkar and C. Krintz. Visualization and analysis of phased behavior in Java programs. In Proceedings of the 3rd <strong>International</strong> Symposium on Principles and Practice of Programming in Java, pages 27–33, 2004. [16] N. Nethercote and J. Seward. Valgrind: A program supervision framework. Electronic Notes in Theoretical Computer Science, 89(2):1–23, 2003. [17] W. D. Pauw, E. Jensen, N. Mitchell, G. Sevitsky, J. Vlissides, and J. Yang. Visualizing the execution of Java programs. In Software Visualization, volume 2269 of Lecture Notes in Computer Science, pages 151–162, 2002. [18] T. Printezis and R. Jones. GCspy: an adaptable heap visualisation framework. In Proceedings of the 17th ACM SIGPLAN <strong>Conference</strong> on Object-Oriented Programming, Systems, Languages, and Applications, pages 343–358, 2002. [19] Y. Sazeides and J. E. Smith. The predictability of data values. In Proceedings of the 30th ACM/IEEE <strong>International</strong> Symposium on Microarchitecture, pages 248–258, 1997. [20] M. Sefika, A. Sane, and R. H. Campbell. Architecture-oriented visualization. In Proceedings of the 11th ACM SIGPLAN <strong>Conference</strong> on Object-Oriented Programming, Systems, Languages, and Applications, pages 389–405, 1996. [21] G. Sevitsky, W. D. Pauw, and R. Konuru. An information exploration tool for performance analysis of Java programs. In Proceedings of TOOLS Europe <strong>Conference</strong>, 2001. [22] J. Singer. Concept assignment as a debugging technique for code generators. In Proceedings of the 5th IEEE <strong>International</strong> Workshop on Source Code Analysis and Manipulation, pages 75–84, 2005. [23] J. Singer and G. Brown. Return value prediction meets information theory. In Proceedings of the <strong>4th</strong> Workshop on Quantitative Aspects of Programming Languages, 2006. To appear in Electronic Notes in Theoretical Computer Science. 39
Investigating Throughput Degradation Behavior of Java Application Servers: A View from Inside a Virtual Machine Feng Xian Computer Science & Engineering University of Nebraska-Lincoln Lincoln, NE 68588-0115 fxian@cse.unl.edu Witawas Srisa-an Computer Science & Engineering University of Nebraska-Lincoln Lincoln, NE 68588-0115 witty@cse.unl.edu Hong Jiang Computer Science & Engineering University of Nebraska-Lincoln Lincoln, NE 68588-0115 jiang@cse.unl.edu ABSTRACT Application servers are gaining popularity as a way for businesses to conduct day-to-day operations. Currently, the most adopted technologies for Application Servers are Java and .NET. While strong emphasis has been placed on the performance and throughput of these servers, only a few research efforts have focused on the degradation behaviors. Specifically, investigating how they perform under stress and factors that affect their throughput degradation behaviors. As a preliminary study, we conducted experiments to observe the throughput degradation behavior of Java application servers and found that the throughput degrades ungracefully. Thus, the goal of this work is three-fold: (i) identifying the primary factors that cause poor throughput degradation, (ii) investigating how these factors affect the throughput degradation, and (iii) observing how changes of algorithms and policies governing these factors affect the throughput degradation. Categories and Subject Descriptors D.3.4 [Programming Language]: Processors—Memory management (garbage collection) General Terms Experimentation, Languages, Performance Keywords Application servers, Throughput, Garbage collection 1. INTRODUCTION Web applications have recently become a method of choice for businesses to provide services and gain visibility in the global market place. For example, eBay is enjoying over 180 million users worldwide. In addition, the advent of Microsoft Office Live 1 , business productivity services, also propels the sophistication of Web 1 Microsoft Office Live, www.officelive.com Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. PPPJ 2006, August 30 – September 1, 2006, Mannheim, Germany Copyright 2006 ACM ...$5.00. services and applications to a new height. The enabling software that allows applications to be served through the Web is referred to as application servers. As of now, industrial observers expect applications servers to be a $27 billion business by the year 2010 2 . Two of the most adopted application server technologies are based on Java and .NET, which occupy about 70% of application servers market share (40% for Java and 30% for .NET) [16]. The major reason for such popularity is due to the rich set of libraries and features provided by these technologies that promote quick development and short time-to-market. On average, such technologies often reduce the code size and development cycle by 50% when compared to older technologies such as CGI written in C/C++ 3 . Application servers often face significant variation in service demands — the higher demands often coincide with “the times when the service has the most value” [23]. Thus, these servers are expected to maintain responsiveness, robustness, and availability regardless of the changing demands. However, the current generation of application servers are not well equipped to meet such expectation as they often fail under heavy workload. For example, on the day that Apple announced the release its Video IPOD, the Apple Store site was down for over one hour due to heavy traffic 4 . In addition, these servers are susceptible to Distributed Denial of Service (DDoS) attacks. One notable example is when a group of Korean high school students launched a DDoS attack on a university Web site to prevent other students from applying 5 . While application server technologies continue to be widely adopted, the knowledge of why these servers fail and how to prevent them from failing is still elusive. To date, very little research has been conducted on the throughput degradation behavior of Java application servers [9, 12]. Specifically, very little information is known about the systems behavior under stress. We have conducted experiments and found that the throughput of Java application servers does not degrade gracefully. A relatively small change in client’s requests (22% increase) can cause the throughput to drop by as much as 75%. This is in contrast to the Apache Web server in which the throughput degrades much more gracefully. This paper reports the results of our extensive study to investigate the reasons behind poor throughput degradation in Java application servers. There are three major contributions resulting from our work. 2 “Web Services to Reach $21 Billion by 2007”, Web Hosting News, http://thewhir.com/marketwatch/idc020503.cfm. 3 Five Reasons to Move to the J2SE 5 Platform, January 2005, http://java.sun.com/developer/technicalArticles/J2SE/5reasons.html 4 from netcraft.com, http://www.netcraft.com 5 “Cyber Crime Behind College Application Server Crash” from http://english.chosun.com/w21data/html/news/200602/200602100025.html 40
Page 1 and 2: Edited by: Ralf Gitzel, Markus Alek
Page 3 and 4: Message from the Chairs Dear confer
Page 5 and 6: Sam Midkiff, Purdue University (USA
Page 7 and 8: Session F: Novel Uses of Java______
Page 10 and 11: The Project Maxwell Assembler Syste
Page 12 and 13: tomated assembler and disassembler
Page 14 and 15: memory address offset mnemonic argu
Page 16 and 17: 5.2 Instruction Templates The assem
Page 18 and 19: ange for a very short restart/debug
Page 20 and 21: Tatoo: an innovative parser generat
Page 22 and 23: In the grammar file an error termin
Page 24 and 25: Figure 3: Push parsers and lexers L
Page 26 and 27: eturn visit((Expr)p1, param); } R v
Page 28: Session B Program and Performance A
Page 31 and 32: Table 1: Use of interfaces and deco
Page 33 and 34: Table 3: Comparison of the situatio
Page 35 and 36: will trigger the creation of many n
Page 37 and 38: Appendix A 10 9 8 7 6 5 4 3 2 1 0 1
Page 39 and 40: Throughout this paper, we make no a
Page 41 and 42: instrumented program and obtained t
Page 43 and 44: Figure 5: Investigation of garbage
Page 45: to the same category—again, this
Page 49 and 50: Figure 1: Apache. Throughput degrad
Page 51 and 52: Minor GC Full GC Workload # of Avg.
Page 53 and 54: Figure 6: Comparing memory and pagi
Page 55 and 56: GenRC on the other hand, allows the
Page 58: Session C Mobile and Distributed Sy
Page 61 and 62: ing a continuous buffer for raw dat
Page 63 and 64: the data arrival speed is more impo
Page 65 and 66: public class StreamingClient { publ
Page 67 and 68: importance of β in our aggregation
Page 69 and 70: Enabling Java Mobile Computing on t
Page 71 and 72: A strongly mobile thread has the ab
Page 73 and 74: a context switch occur. The invoked
Page 75 and 76: above phases. Now, the new stack ha
Page 77 and 78: 5 frames 15 frames 25 frames Pure d
Page 79 and 80: Juxta-Cat: A JXTA-based platform fo
Page 81 and 82: Figure 1: JXTA Architecture. 3. JUX
Page 83 and 84: • Send a discovery query to the p
Page 85 and 86: The best candidate is then the one
Page 87 and 88: Local Hosts=2 Hosts=4 Hosts=8 Hosts
Page 90: Session D Resource and Object Manag
Page 93 and 94: Enterprise Edition (J2EE). It enabl
Page 95 and 96: As pictured in Figure 4, JDOSecure
Page 97 and 98:
Methods of a PersistenceManager, th
Page 99 and 100:
Datenmodell abstrahiert user role,
Page 101 and 102:
An Extensible Mechanism for Long-Te
Page 103 and 104:
missing object references in the de
Page 105 and 106:
4.2 Mapping the name spaces of the
Page 107 and 108:
(a) (b) ColorSliderPanel0 color
Page 109 and 110:
8. REFERENCES [1] Abu-Ghazaleh, N.,
Page 111 and 112:
permission by process. In other wor
Page 113 and 114:
The processor then refers to the en
Page 115 and 116:
1: // Protection domain 2: struct p
Page 117 and 118:
Table 3: Frequency of JNI calls tha
Page 119 and 120:
[13] Intel Corporation. IA-32 Intel
Page 121 and 122:
01 try { 02 ... 03 } finally { 04 t
Page 123 and 124:
2. FRAMEWORK The Framework for Unif
Page 125 and 126:
ManagedInputStream ResourceGroup Ma
Page 127 and 128:
18. throw ‡ 1. release 17. cleanu
Page 129 and 130:
3. FUTURE WORK The ability to split
Page 131 and 132:
124
Page 133 and 134:
UML sequence diagrams are among the
Page 135 and 136:
diagrams, and behavioral (dynamic)
Page 137 and 138:
the official scripting language for
Page 139 and 140:
Apache's XML Graphics Project. A cu
Page 141 and 142:
Java Debug Interface (JDI). In Revi
Page 143 and 144:
1.3 JML 1.3.1 Overview JML, the Jav
Page 145 and 146:
The Usage of CANAPA is fairly strai
Page 147 and 148:
*@non_null@*/ String str = attribut
Page 149 and 150:
142
Page 151 and 152:
parallel and distributed versions o
Page 153 and 154:
RingElem CextendsRingElem GenPolyno
Page 155 and 156:
RingElem +isZERO():bolean CextendsR
Page 157 and 158:
class constructors with the actual
Page 159 and 160:
plemented via a distributed hash ta
Page 161 and 162:
which are common nowadays. The reus
Page 163 and 164:
Derivative Contract Component Repos
Page 165 and 166:
stepwise execution create Derivativ
Page 167 and 168:
5.4.1 Structural Constraints Struct
Page 169 and 170:
into the conceptual foundation of n
Page 171 and 172:
different implementation and is mor
Page 173 and 174:
the service from the root. It allow
Page 175 and 176:
model: 1. Servlet [6] adapter compo
Page 177 and 178:
y possibly different service, where
Page 179 and 180:
or the fact that widgets extend ser
Page 181 and 182:
174
Page 183 and 184:
The idea of Java 5.0 type inference
Page 185 and 186:
Source := (class | interface)∗ cl
Page 187 and 188:
5. IMPLEMENTATION In order to prese
Page 189 and 190:
Infinite Streams in Java Dominik Gr
Page 191 and 192:
} private static LinkedStream fibon
Page 193 and 194:
of the f stream in order to compute
Page 195 and 196:
Interaction among Objects via Roles
Page 197 and 198:
(a) (b) (c) (d) (e) Figure 1: The p
Page 199 and 200:
class Printer { private int totalPr
Page 201 and 202:
Experiences of using the Dagstuhl M
Page 203 and 204:
Metric Definition Java .class files
Page 205 and 206:
scription of the metric values. Non
Page 207 and 208:
Figure 1: Results from the J-vestig
Page 209 and 210:
an error is subsequently generated
Page 211 and 212:
3. BASIC TERMINOLOGY As object-orie
Page 213 and 214:
• subtyping • (implementation)
Page 215 and 216:
Improving the Quality of Programmin
Page 217 and 218:
Results of online checks (shortened
Page 219 and 220:
212
Page 221 and 222:
214
Page 223 and 224:
Experiences With Hierarchy-Based Co
Page 225 and 226:
Sub View Child DataField 0..n Ke
Page 227 and 228:
Figure 8 - Actual State Charts elem
Page 229 and 230:
associations, which may result in r
Page 231 and 232:
M3PS: A Multi-Platform P2P System B
Page 233 and 234:
In following, we will explain in de
Page 235 and 236:
Figure 10. JDP in Windows XP. Figur
Page 237 and 238:
Mapping Clouds of SOA- and Business
Page 239 and 240:
the technical SOA events (from the
Page 241 and 242:
component and the business process
Page 243 and 244:
Figure 13. “Business Value of Dat
Page 245 and 246:
Solaris of SUN. This platform provi
Page 247 and 248:
status change of an application is
Page 249 and 250:
coming up, is presently discussing
Page 251:
ISBN: 3-939352-05-5 ISBN: 978-3-939
show all

4th International Conference on Principles and Practices ... - MADOC

Create successful ePaper yourself

Delete template?

Save as template?