T
tombrogan3
Hi, I'm writing a service which has to monitor a database looking for
new feeds (basically a few hundred thousand rows with a common id).
When it finds a new feed I can either:
1) Process it on the current thread (not ideal as the app must be seen
to be responding to new feeds straight away, and this processing can
take up to an hour).
2) Launch a new thread to process the feed.
3) Launch a new process to process the feed.
Are there any advantages / disadvantages to launching processes rather
than threads? Would the performance be better?
Obviously both threads / processes will access the same database, but
that's the only thing they have in common. There are no other shared
resources or values.
Cheers for any help,
Tom.
new feeds (basically a few hundred thousand rows with a common id).
When it finds a new feed I can either:
1) Process it on the current thread (not ideal as the app must be seen
to be responding to new feeds straight away, and this processing can
take up to an hour).
2) Launch a new thread to process the feed.
3) Launch a new process to process the feed.
Are there any advantages / disadvantages to launching processes rather
than threads? Would the performance be better?
Obviously both threads / processes will access the same database, but
that's the only thing they have in common. There are no other shared
resources or values.
Cheers for any help,
Tom.