Thanks for quick response. please see my comments
1. Connect : if datasever then DBI, if host then ssh or tcp
2. Process: remotely on the server if host.
if database then execute few sql query
3. How long will that processing run?
>> for few server it might take hour, for few it will take less.
4. Get the data: How much data?
>> data will vary from dataserver to dataserver, depending on activities on server. it can be in KB but not more than 1-2 MB. Since we are planning to run very frequently so we can handle data properly.
5. Write to file:
Just read & write as is, or read, process locally and write?
>>read, process locally and then write.
6. Connect again may be after 1/2 hour:
Exactly half an hour? Or as quickly as possible after all other servers have been serviced?
>> this we will decide, depending onnature od dataserver we can decide interval time.
7. What determines the frequency of reconnection? How important is the timing? Must it be done to the second, or is 'best endevours' good enough?
>>depends on interval time or we can decide the best way. idea is to collect data after every 10 minutes or 30 minutes, from each server
8. should run for many servers ( may be 1000s):
You don't yet know? How many 1000s?
>>This will keep growing in future. initially we are targetting for 1000.
Thanks | [reply] |
for few server it might take hour, ... idea is to collect data after every 10 minutes or 30 minutes,
So, you going to collect data that takes an hour to query, every 10 or 30 minutes.
depends on interval time or we can decide the best way.
What is "the interval time"? Like, a value you choose to program? In which case, how is that different from "or we can decide the best way."?
Reading between the lines, what I think you are saying is; "as often as possible"? If so, that is good, because it is very easy to program "as often as possible".
But if it is imperative that server X be serviced every 10 minutes; and server Y every 30 minutes; and server Z every 19.27071 minutes; things get much, much more complicated.
idea is to collect data after every 10 minutes or 30 minutes, from each server
"the idea"? This sounds like a "suck thumb and wave finger in air" metric. And that is no basis upon which to make design decisions.
So far, there is so much contradiction in your 'spec', it is pretty much impossible to make any real assessment of whether a single, multi-threaded program is a suitable way of tackling the problem. You'll need to be a lot clearer in specifiying the actual requirements, rather than speculative "it would be nice ifs".
Another question: why are you considering threads rather than processes?
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
thanks again and sorry for being not very clear in my reply.
we want to collect infromation from each server in every 30 minutes. for time being we will not consider servers which takes >=1 hour
We will have one group which will contain 30 data servers, if we process each server sequentially, might not be good idea. If we use thread then we can process parallely, execution will be faster and will be easy to manage.
Why not considring process ?
since forking many process( may be 100s) in one time and monitoring them will be complex. Also will consume lots of memory. But if you think forking is better option than threads, we can consider that option as well.
| [reply] |