Hi guys, Does anyone know how jBASE transactionality works in details? I can imagine some algorithms and it seems to me that Jim said that jEDI creates changes buffer in memory.
Questions are following: a) How does is happen that jBASE is transactional? Assume multiple writes are required to commit transaction. Assume that filesystem is not transactional or WRITEs are performed on directories (not J4 files). b) Does file sizing influences on a transaction performance - mean WRITE / DELETE operations? I think it does not so much (my understanding: file sizing problem occurs when transaction is commited and records flushed to disk; but does not exists as long as transaction is open). Imagine that some brilliant guy created single transaction for 300000-900000 (900k) changes. It lasted almost 7h, but I wonder how jBASE behave. c) Does number of changes inside transaction influence on READ / WRITE / DELETE time? (here bottleneck can be found I think). jBASE needs to scan somehow changes buffer, right? Is it efficient mechanism? d) What can you do if you do not have influence on how code is written and how transaction is managed? I know that answer for first 2 questions is "check by yourself"... :) I will eventually try to check by myself and share results. Kind regards Pawel ---------------------------------------------------- Jesteś fanem Kasi Zielińskiej i Barw Szcześcia? Zagłosuj w plebiscycie Telekamery 2009! http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fkzielinska.html&sid=604 --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
