Seems I may have dug myself a big hole
I have a BO FlightLog which contains details of an aircraft's flight
Flightlog has a many to one relationship with BO FlyingSheet and FlyingSheet has one to many relationship with FlightLog. FlyingSheets represent one Day's flying and the avg number of FlighLogs is 60 per day (max around 100)
FlightLog also 2 x many to one relationships with BO Members, one for Pilot 1 (P1) and the other for the pupil (P2) Each Member also has 2 x one to many relationships with FlightLog for P1 and P2.
FlightLog also has a many to one relationship (with a reciprocal one to many) to BO Aircraft
The system works fine logically and provides a) Daily flying sheets, b) Individual Pilot log books for their flights at both P1 and P2 and c) Individual Aircraft Log Books The system has been in use since April 2010
Both FlightLog and Members have a very complex set of rules
My Problem - Our Launch Administrators are reporting that for some combinations of Pilots and Aircraft it can take up to a minute to save a newly created Flightlog.
Some numbers: for a FlightLog where Member P1 has 1676 and Member P2 has 168 in an aircraft with 1788 flights recorded - Creating a new Flightlog - 55 seconds
For a FlighLog where P1 has 50 flights and no P2 (A solo flight) in an aircraft with 1788 records - 2 to 3 seconds which - given the app is web based is acceptable.
For A FlightLog where P1 has 1676 flights, No P2 in an aircraft that has 1788 flights - 36 seconds
I should add that BO Aircraft has no rules and doesn't appear to be the problem
My deduction is that there is some rule in either the Members BO or the FlightLog BO that is causing the rule engine to recalculate many times but I can't seem to trace it in the logs.
Can't use the test BS - insufficient data
Can't use the Main Logger because every minute, the schedule rules trigger and wipe out all previous events
Can't seem to log to file - for some reason, nothing ever appears in it except the schedule rules, unless I'm not turning it on early enough to capture the events
Support - is this something you could look at with a support ticket. My problem is I'd somehow have to send you the complete mysql file since it would be impossible to replicate with minimal data. Of course with your experience you might be able to spot the problem just by looking at how the rules are configured.
Showing you live using BeamYourScreen is an option
