Hi BrowserUk,

Please find the answers inline

What type of application servers are involved?

1. These servers are an i/f to the db so instead of firing query to a specifc table all we have

What type of queries are you "firing off"?

2. The queries are simple select queries though can have 100 colummns and can retrun 10K rows as well.

What kind of network bandwidth will the server have?

3. Not Sure

What kind of network latency is involved?

4. Not Sure

What type of "comparison"s are you doing? (Simple string compare or something more complicated.)

5. The o/p returned from prod and test are first string compared . if there is some error then we go into lower levels of comparison.The app server have a charecteristics of messing up with the order of the results returned . so they are sorted first then row by row comparison takes place.There are various clauses that one needs to take care one is exclude certain columns from comparison, compare only certain keys ( these are just a few) in all the comparison is not simple

Why are you redeveloping?

6.1 The QA team would not have to rush to the devlopers each time there is some problem or some enhacement.They know perl better.

6.2 Perl is widely known two be very good is string comparison.

6.3 I have been told by my Lead)(i have to make it and make it good else i would be kicked out :-))

What is wrong with the existing forking solution?

7.1 It is not scalable/extendable

7.2 Comparison logic takes a lot of time.

What language was employed in thae previous solution?

8. C++

Will the 12-cpu box be dedicated to just this task?

9. That i what i have been told but it can go down to 4 cpu also

What are the project requirements?

10. Rewrite/Redesign the C++ code in Perl 5 so that it takes lesser time and is maintaineable.

Which of those is the existing code not meeting? And by how much is it missing it or them?

11. The Suite takes 3 weeks to run i mean the entire cycle i have to bring it down

In reply to Re^16: Problem in Inter Process Communication by libvenus
in thread Problem in Inter Process Communication by libvenus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.