• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Difference reading in from URL in direct connect/deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Difference reading in from URL in direct connect/deployment


  • Subject: Re: Difference reading in from URL in direct connect/deployment
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 28 Dec 2007 07:09:43 -0800

It could also be that the deployed app has less memory allocated to the JVM so it is spending lots of time garbage collecting.

Chuck

On Dec 28, 2007, at 5:55 AM, Kieran Kelleher wrote:

Why not put some timers on parts of the code ... apache commons Lang StopWatch class is useful for this or just use System time in milliseconds. In loop scenario, you could time different parts of the code separately and build and average as the loop progresses and log that out. This might give insight into machine differences.

The java on Mac Mini implementation (by Apple) might be different to the one on your Linux box. Default buffer sizes might be different also.


On Dec 28, 2007, at 7:57 AM, ute Hoffmann wrote:


Am 28.12.2007 um 13:26 schrieb James Nugent:

When testing the app via direct connect I get the data down in about 3 Minutes, parsing and all.
More than 10 Minutes for reading in the exact same data and do the exact same parsing????
How can that be, given that I have a ISDN-connection and the webserver the deployed App lives on has a much better connection?


Is the development machine significantly faster than the web server? I'd have thought that most of the time would be spend parsing rather than downloading.

I do not know. The development machine is a Intel mac mini, cheapest version. The WebServer is a linux which should be as good as the mac mini, I think...


I have a lot of logging going on as I had a Long response which somehow could not deal properly with the download and went into an infinite loop - don't ask me why...

I'm rather sure it is not the parsing that takes so long. I parse on each request only as much of the XML as I have to show and that means only a small part of the XML gets parsed at once.

But he logs, when he has the data available in a String var and this is the bottle neck, as far as I can see. So perhaps the reading in is the real problem as he has to process each line and there are many lines....if one downloads that XML into firefoy and saves it from there to an pdf, one gets 256 pages...



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net


This email sent to email@hidden


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Difference reading in from URL in direct connect/deployment (From: ute Hoffmann <email@hidden>)
 >Re: Difference reading in from URL in direct connect/deployment (From: James Nugent <email@hidden>)
 >Re: Difference reading in from URL in direct connect/deployment (From: ute Hoffmann <email@hidden>)
 >Re: Difference reading in from URL in direct connect/deployment (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: Re: AjaxExample Grid will not work
  • Next by Date: Re: Wonder 4 upgrade exception
  • Previous by thread: Re: Difference reading in from URL in direct connect/deployment
  • Next by thread: Wonder 4 upgrade exception
  • Index(es):
    • Date
    • Thread