|
|
Re: Serialized Java objects remains on disk after deserializing [message #656247 is a reply to message #655897] |
Thu, 24 February 2011 16:44 |
Eclipse User |
|
|
|
Originally posted by: juergen.schumacher.attensity.com
Am 23.02.2011, 09:22 Uhr, schrieb Andrej Rosenheinrich =
<andrej.rosenheinrich@unister-gmbh.de>:
> Can someone confirm if those thoughts are right? Or would it cause =
> sidefeffects to delete those files?
Sorry, I'm not very accustomed to the Web Crawer, so I'm not sure. From =
=
reading the code,
I could imagine situations where a URL is visited twice during crawling =
=
and the second visit
happens before the first visit is completely processed, so the file woul=
d =
not be recreated
and the processing of the first visit would delete it before the second =
=
visit can read it.
Or something like this. On the other hand this sounds like a dubious =
behaviour anyway (:
Daniel, Tom, do you know anything about this?
Regards,
J=C3=BCrgen
|
|
|
|
|
Re: Serialized Java objects remains on disk after deserializing [message #658164 is a reply to message #657795] |
Mon, 07 March 2011 08:55 |
Eclipse User |
|
|
|
Originally posted by: juergen.schumacher.attensity.com
Hi,
Am 04.03.2011, 06:45 Uhr, schrieb SMILANewBee <nils.thieme@unister.de>:
> Hello,
>
> we have also noticed, that deleting the files instantly a performance =
=
> decline was detected. We have too many hard drives accesses. So it wou=
ld =
> be better if the files would be deleted blockwise.
Could you create a bugzilla issue for this, so we are able to track it?
Further discussion should be done in bugzilla then.
Thank you!
Regards,
J=C3=BCrgen.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02164 seconds