[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: How does remote ABL broker distribute client requests to available servers?

  • Thread starter Thread starter ChUIMonster
  • Start date Start date
Status
Not open for further replies.
C

ChUIMonster

Guest
For 4gl brokers I almost always use -Mi 1 -- that means "round robin" and _generally_ provides the best balance. The sql server is multi-threaded so for SQL brokers I will use -Mi = -Ma. You shouldn't use "both" brokers but, if you do, -Mi = -Ma is probably wiser. That way you are much less likely to get painted into a corner where all the servers are taken by 4gl or sql before the other type has a chance to start any. There are a lot of KB entries that are badly outdated or very misguided. -Ma 5 is a very old recommendation. YMMV but, in a very "broad brush" kind of way, current systems can probably easily support -Ma 10 or 20. -Ma 100 OTOH is probably not such a good idea. As you say, the time slicing means that one bad query can either cause a lot of problems directly or perform very poorly in such an environment. The DBA has to also understand the application and how well, or how poorly, it is written and what the characteristics of the queries in the application are. There are a number of sources of information about what is going on with remote servers in the VSTs. ProTop has a couple of handy views of client/server activity that are based on that data: ┌──────────────────────────────────────────────────────────────────── Login Broker Config ─────────────────────────────────────────────────────────────────────┐ │ Typ v IPver PID -S -minport -maxport -PendCx -Mm -Mpb -Ma -Mi Cnx Cnx% SQLTrc SQLWUp SQLcurs SQLstck SQLstmt SQLtmpb SQLtmpd SQLtmpz │ │ ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │ │ >SQL IPV4 45979 9050 26200 26399 0 1024 16 5 1 0 0% OFF OFF 0 0 0 0 0 0 │ │ SQL IPV4 45965 9000 25100 25199 0 1024 6 5 1 0 0% OFF OFF 0 0 0 0 0 0 │ │ BOTH IPV4 45715 9030 1025 2000 0 8192 0 4 1 0 ? OFF ON 0 0 0 0 0 0 │ │ ABL IPV4 45951 9990 20000 21999 0 8192 100 5 1 0 0% OFF OFF 0 0 0 0 0 0 │ ┌────────────────────────────────────────────────────────────────────── Server Activity ───────────────────────────────────────────────────────────────────────┐ │ Srv Type Port Cnx Max QryRcvd recSndQry bytSndQry MsgRcvd RecRcvd rr/msg MsgSent RecSent rs/msg MB Sent v MB Rcvd RcvdSz SendSz │ │ ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── │ │ > 9999 Total 0 48 449 614 3 960 1502 0 0.00 871 1902 2.18 0.56 0.38 262 678 │ │ 24 Auto 20028 1 5 570 3 892 1096 0 0.00 579 1538 2.65 0.49 0.29 281 878 │ │ 46 Auto 20053 1 5 10 7 2131 69 0 0.00 54 73 1.37 0.02 0.01 172 414 │ │ 25 Auto 20029 1 5 12 7 1576 130 0 0.00 109 88 0.81 0.02 0.03 248 171 │ │ 28 Auto 20032 1 5 6 8 2301 47 0 0.00 37 49 1.32 0.01 0.01 179 390 │ │ 22 Auto 20026 1 5 3 8 1507 24 0 0.00 14 21 1.54 0.00 0.01 221 286 │ │ 20 Auto 20024 1 5 1 15 2269 16 0 0.00 9 20 2.13 0.00 0.00 196 317 │ │ 15 Auto 20019 1 5 2 12 1690 15 0 0.00 9 19 2.20 0.00 0.00 208 314 │ │ 21 Auto 20025 1 5 2 7 1477 17 0 0.00 10 13 1.34 0.00 0.00 219 266 │ │ 14 Auto 20018 1 5 2 6 1279 17 0 0.00 10 12 1.20 0.00 0.00 212 256 │ │ 18 Auto 20022 1 5 2 9 1461 15 0 0.01 9 16 1.73 0.00 0.00 204 270 │ │ 17 Auto 20021 1 5 1 10 1897 15 0 0.00 9 13 1.50 0.00 0.00 208 280 │ │ 23 Auto 20027 1 5 1 10 1641 13 0 0.00 8 12 1.61 0.00 0.00 213 277 │ │ 16 Auto 20020 1 5 1 10 1931 12 0 0.00 7 10 1.48 0.00 0.00 198 280 │ │ 19 Auto 20023 1 5 1 12 2124 9 0 0.00 5 9 1.62 0.00 0.00 203 281 │ │ 62 Auto 20069 1 5 0 35 4290 2 0 0.00 1 3 2.92 0.00 0.00 165 357 │ │ 47 Auto 20054 1 5 0 35 4290 2 0 0.00 1 3 2.92 0.00 0.00 165 357 │ │ 36 Auto 20041 1 5 0 30 3211 1 0 0.07 1 3 3.00 0.00 0.00 112 321 │ │ 750 Inact 0 0 0 0 0 0 0 0 0.00 0 0 0.00 0.00 0.00 0 0 │ │ 749 Inact 0 0 0 0 0 0 0 0 0.00 0 0 0.00 0.00 0.00 0 0 │ │ 748 Inact 0 0 0 0 0 0 0 0 0.00 0 0 0.00 0.00 0.00 0 0 │

Continue reading...
 
Status
Not open for further replies.
Back
Top