• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

JVM startup time problem

Ranch Hand
Posts: 260
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have developed a small communcation application (proxylet) deployed in given enviroment.

java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
using the sipp ( Open Source test tool / traffic generator for the SIP protocol), when I genrate the 20 call per scee,40 cps,60 cps.
my application gets start and I get lots of call failure.however if genrate
around 5000 calls before actual testing ,it gives me desired result.
every time to get the desired result I have to warmup the jvm with the minimun 5000 call at 20 or 40 cps

kindly suggest me why is nessarry to give this startup calls. and how can I avoid it

your valuable suggestion will be great help for me
Vijay Kumar
author and iconoclast
Posts: 24207
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You have posted this same question, worded differently, several times now. People have tried to ask you questions to draw you out, but you haven't supplied the requested information.

Have you done any reading about HotSpot and how it works? It uses profiling data from running your code to decide how to optimize it; as a result, many applications need a little "warmup" time before they reach their performance peak. In addition, a method has to run a certain number of times before HotSpot will bother looking at it; the exact number depends on various options.

You seem to have done a bit of work on finding out the answer yourself at one point, asking about the "-XXCompileThreshold" command-line switch. But did you experiment with this? What values did you try? What was the result? What other switches are you using? Have you tried adjusting the GC parameters? Have you Googled "XXCompileThreshold" for advice on using this switch, or other related HotSpot features?

If you just keep asking the same question in the same words, over and over again, it's unlikely you'll get any more useful information. But if you have a dialog, by answering replies in one single thread for this one single topic, then over time, information about your problem accumulates in one place, and someone might be able to help you.
    Bookmark Topic Watch Topic
  • New Topic