1. A method for transactionally consistent replay of application workloads, the method implemented in a computer system having at least one processor and at least one memory, the method comprising:
during a replay phase, in which a plurality of application requests that were previously submitted to a capture-phase application server system during a capture phase are being replayed against a replay-phase application server system, receiving, at a database server system, a database request to execute a database command against a database;
wherein the plurality of application requests replayed against the replay-phase application server system represents a captured application server system workload;
wherein the database request specifies an application request identifier that identifies a particular application request of the plurality of application requests;
wherein the particular application request caused the database command to be executed previously during the capture phase;
in response to receiving the database request, determining, based on the application request identifier in the database request, whether to delay execution of the database command at least until a particular database transaction has been committed during the replay phase.
2. The method of claim 1, further comprising:
determining whether to delay execution of the database command based on a database sequence number assigned to the database command during the capture phase and based on a database sequence number assigned to the particular database transaction during the capture phase.
3. The method of claim 1, wherein, during the capture phase, a database request comprising the database command was received at a capture phase database server system after the particular database transaction was committed to a capture phase database; and wherein, during the replay phase, the database request comprising the database command is received at the database server system before the particular database transaction is committed.
4. The method of claim 1, wherein the database command is a commit action.
5. The method of claim 1, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, the method further comprising:
determining, based on the application request identifier and the text of the database command, a database sequence number that was assigned to the database command during the capture phase.
6. The method of claim 1, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the particular application request, when replayed during the replay phase, causes the plurality of database commands to be received at the database server system in a different order than they were received at a capture phase database server system during the capture phase, the method further comprising:
in response to detecting the different order of the plurality of database commands during the replay phase, relaxing transactional consistency for the particular application request during the replay phase.
7. The method of claim 1, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the particular application request, when replayed during the replay phase, causes a database command to be received at the database server system that was not received as one of the plurality of database commands at a capture phase database server system during the capture phase, the method further comprising:
in response to detecting receipt of the database command during the replay phase that was not received during the capture phase, relaxing transactional consistency for the particular application request during the replay phase.
8. The method of claim 1, wherein during the replay phase a communication channel is maintained between one or more replay clients replaying the plurality of application requests and the database server system, the method further comprising:
receiving, from the one or more replay clients over the communication channel, an application request identifier of an application request that previously caused the particular database transaction to be committed to a database during the capture phase, and
in response to receiving the application request identifier over the communication channel, determining that execution of the database command should not be delayed until the particular database transaction has been committed during the replay phase.
9. The method of claim 1, wherein the capture-phase application server system and the replay-phase application server system is the same application server system.
10. A database system having one or more processors, the system comprising:
a database replay capture mechanism configured to perform, during a capture phase in which a plurality of application requests are submitted to a capture-phase application server system,
obtaining an application request identifier of a particular application request of the plurality of application requests,
assigning a database sequence number to a particular database command caused to be executed against a database by the particular application request, and
recording, in a capture log, data that reflects the particular database command in association with the database sequence number and the application request identifier;
a database replay synchronizing mechanism configured to perform, during a replay phase in which the particular application request that was previously submitted to the capture-phase application server system during the capture phase is being replayed against a replay-phase application server system,
obtaining the application request identifier of the particular application request,
determining, based on the application request identifier, whether to delay replay-phase execution of the database command at least until a particular replay-phase database transaction has been committed.
11. The system of claim 10, wherein the database replay synchronization mechanism is further configured to perform:
determining whether to delay execution of the database command based on a database sequence number assigned to the database command during the capture phase and based on a database sequence number assigned to the particular database transaction during the capture phase.
12. The system of claim 10, wherein, during the capture phase, a database request comprising the database command was received at a capture phase database server system after the particular database transaction was committed to a capture phase database; and wherein, during the replay phase, the database request comprising the database command is received at the database server system before the particular database transaction is committed.
13. The system of claim 10, wherein the database command is a commit action.
14. The system of claim 10, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the database replay synchronization mechanism is further configured to perform:
determining, based on the application request identifier and the text of the database command, a database sequence number that was assigned to the database command during the capture phase.
15. The system of claim 10, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the particular application request, when replayed during the replay phase, causes the plurality of database commands to be received at the database server system in a different order than they were received at a capture phase database server system during the capture phase, and wherein the database replay synchronization mechanism is further configured to perform:
in response to detecting the different order of the plurality of database commands during the replay phase, relaxing transactional consistency for the particular application request during the replay phase.
16. The system of claim 10, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the particular application request, when replayed during the replay phase, causes a database command to be received at the database server system that was not received as one of the plurality of database commands at a capture phase database server system during the capture phase, and wherein the database replay synchronization mechanism is further configured to perform:
in response to detecting receipt of the database command during the replay phase that was not received during the capture phase, relaxing transactional consistency for the particular application request during the replay phase.
17. The system of claim 10, wherein during the replay phase a communication channel is maintained between one or more replay clients replaying the plurality of application requests and the database server system, and wherein the database replay synchronization mechanism is further configured to perform:
receiving, from the one or more replay clients over the communication channel, an application request identifier of an application request that previously caused the particular database transaction to be committed to a database during the capture phase, and
in response to receiving the application request identifier over the communication channel, determining that execution of the database command should not be delayed until the particular database transaction has been committed during the replay phase.
18. The system of claim 10, wherein the capture-phase application server system and the replay-phase application server system is the same application server system.
19. One or more non-transitory computer-readable media storing instructions which, when executed by one or more processors, cause performance of a method for transactionally consistent replay of application workloads, the method comprising:
during a replay phase, in which a plurality of application requests that were previously submitted to a capture-phase application server system during a capture phase are being replayed against a replay-phase application server system, receiving, at a database server system, a database request to execute a database command against a database;
wherein the plurality of application requests replayed against the replay-phase application server system represents a captured application server system workload;
wherein the database request specifies an application request identifier that identifies a particular application request of the plurality of application requests;
wherein the particular application request caused the database command to be executed previously during the capture phase;
in response to receiving the database request, determining, based on the application request identifier in the database request, whether to delay execution of the database command at least until a particular database transaction has been committed during the replay phase.
20. The one or more non-transitory computer-readable media of claim 19, the method further comprising:
determining whether to delay execution of the database command based on a database sequence number assigned to the database command during the capture phase and based on a database sequence number assigned to the particular database transaction during the capture phase.
21. The one or more non-transitory computer-readable media of claim 19, wherein, during the capture phase, a database request comprising the database command was received at a capture phase database server system after the particular database transaction was committed to a capture phase database; and wherein, during the replay phase, the database request comprising the database command is received at the database server system before the particular database transaction is committed.
22. The one or more non-transitory computer-readable media of claim 19, wherein the database command is a commit action.
23. The one or more non-transitory computer-readable media of claim 19, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, the method further comprising:
determining, based on the application request identifier and the text of the database command, a database sequence number that was assigned to the database command during the capture phase.
24. The one or more non-transitory computer-readable media of claim 19, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the particular application request, when replayed during the replay phase, causes the plurality of database commands to be received at the database server system in a different order than they were received at a capture phase database server system during the capture phase, the method further comprising:
in response to detecting the different order of the plurality of database commands during the replay phase, relaxing transactional consistency for the particular application request during the replay phase.
25. The one or more non-transitory computer-readable media of claim 19, wherein the particular application request caused a plurality of database commands including the database command to be executed previously during the capture phase, and wherein the particular application request, when replayed during the replay phase, causes a database command to be received at the database server system that was not received as one of the plurality of database commands at a capture phase database server system during the capture phase, the method further comprising:
in response to detecting receipt of the database command during the replay phase that was not received during the capture phase, relaxing transactional consistency for the particular application request during the replay phase.
26. The one or more non-transitory computer-readable media of claim 19, wherein during the replay phase a communication channel is maintained between one or more replay clients replaying the plurality of application requests and the database server system, the method further comprising:
receiving, from the one or more replay clients over the communication channel, an application request identifier of an application request that previously caused the particular database transaction to be committed to a database during the capture phase, and
in response to receiving the application request identifier over the communication channel, determining that execution of the database command should not be delayed until the particular database transaction has been committed during the replay phase.
27. The one or more non-transitory computer-readable media of claim 19, wherein the capture-phase application server system and the replay-phase application server system is the same application server system.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A communication structure, comprising:
a mobile terminal ground plane including a ground point;
a primary radiator that is electrically coupled to the ground point;
a first antenna branch that includes a first filter circuit that is coupled between a first point on the primary radiator and a first antenna port and that corresponds to a first frequency band; and
a second antenna branch that includes a second filter circuit that is coupled between a second point on the primary radiator and a second antenna port that corresponds to a second frequency band that is different from the first frequency band,
wherein the primary radiator comprises a length of about 30 mm and is arranged at a distance in a range of about 2 mm to about 4 mm from the ground plane,
wherein the first point on the primary radiator is located at a position along the primary radiator to provide an impedance match, and
wherein the second antenna branch is located at a position along the primary radiator that is in a range of about \u2153 of a distance from the first point on the primary radiator to an end of the primary radiator to about \xbd of the distance from the first point on the primary radiator to the end of the primary radiator.
2. A communication structure according to claim 1, wherein the first filter circuit comprises a first bandpass filter that is configured to provide a low ohmic path to signals corresponding to frequencies at least of about 1.575 GHz.
3. A communication structure according to claim 1, wherein the second filter circuit is operable to filter out a signal that includes frequencies in the first frequency band,
wherein the first filter circuit is operable to filter out a signal that includes frequencies in the second frequency band, and
wherein a difference between the first frequency band and the second frequency band provides frequency isolation between the first antenna port and the second antenna port.
4. A communication structure according to claim 1, wherein the first antenna branch is operable to resonate at the first frequency band,
wherein the second antenna branch is operable to resonate at the second frequency band, and
wherein the first frequency band is substantially adjacent the second frequency band to provide antenna performance over a combined bandwidth that substantially includes the first frequency band and the second frequency band.
5. A communication structure according to claim 4, wherein the combined bandwidth comprises a frequency band including a frequency range of about 700 Mhz to about 960 MHz.
6. A communication structure according to claim 5, further comprising a filter that is operable to selectively activate the communication structure corresponding to one of the first frequency band and the second frequency band.
7. A communication structure according to claim 1, further comprising a matching element coupled between the ground point and the primary radiator, wherein the matching element is operable to increase a length between the primary radiator and the ground point.
8. A communication structure according to claim 7, wherein the matching element comprises an inductor that includes andor is series coupled with a capacitor.
9. A communication structure according to claim 1, further comprising a first capacitor coupled between the ground point and the primary radiator,
wherein the first point on the primary radiator is between the second point on the primary radiator and the first capacitor,
wherein the first filter circuit comprises a first inductor having a first inductance and the first antenna port comprises a frequency modulated (FM) radio band port,
wherein the second filter circuit comprises a second capacitor arranged in parallel with a second inductor than includes a second inductance that is less than the first inductance, and
wherein the first capacitor and the second capacitor have a substantially similar capacitance value.
10. A communication structure according to claim 1 further comprising:
an RF transceiver including an RF transmitter coupled to the primary radiator and an RF receiver coupled to the primary radiator;
a user interface including a speaker and a microphone; and
a processor coupled between the user interface and the transceiver, wherein the processor is configured to receive radiotelephone communications through the receiver and to reproduce audio communications using the speaker responsive to the received radiotelephone communications and to generate radiotelephone communications for transmission through the transmitter responsive to audio input received through the microphone.
11. A communication structure according to claim 10 further comprising:
a printed circuit board (PCB) including electrically conductive traces provided at different planes thereof, wherein portions of the processor, user interface, andor transceiver are implemented as electronic components provided on the printed circuit board, and wherein the ground plane is provided as an electrically conductive layer at one or more planes of the printed circuit board.
12. A communication structure, comprising:
a mobile terminal ground plane including a ground point;
primary radiator that is electrically coupled to the ground point;
a first antenna branch that includes a first filter circuit that is coupled between a first point on the primary radiator and a first antenna port and that corresponds to a first frequency band; and
a second antenna branch that includes a second filter circuit that is coupled between a second point on the primary radiator and a second antenna port that corresponds to a second frequency band that is different from the first frequency band, wherein the first filter circuit comprises:
a first capacitor that is coupled between the first point on the primary radiator and the first antenna port;
a first inductor that includes a first terminal that is coupled to the first point on the primary radiator; and
a second capacitor that includes a first terminal that is coupled to a second terminal of the first inductor and a second terminal that is coupled to the first antenna port, and
wherein the second filter circuit comprises:
a second inductor that is coupled between the second point on the primary radiator and the second antenna port;
a third capacitor that includes a first terminal that is coupled to the second point on the primary radiator; and
a third inductor that includes a first terminal that is coupled to a second terminal of the third capacitor and a second terminal that is coupled to the second antenna port.
13. A communication structure according to claim 12, wherein at least one of the first inductor, the second inductor andor the third inductor comprises a multi-layer chip inductor.
14. A communication structure according to claim 12, wherein at least one of the first inductor, the second inductor and the third inductor comprises a wirewound inductor.
15. A communication structure, comprising:
a mobile terminal ground plane including a ground point;
a primary radiator that is electrically coupled to the ground point;
a first antenna branch that includes a first filter circuit that is coupled between a first point on the primary radiator and a first antenna port and that corresponds to a first frequency band; and
a second antenna branch that includes a second filter circuit that is coupled between a second point on the primary radiator and a second antenna port that corresponds to a second frequency band that is different from the first frequency band,
wherein the first antenna branch, a first portion of the primary radiator that is between the first point on the primary radiator and the second point on the primary radiator, and a second portion of the primary radiator that is beyond the second point on the primary radiator are collectively operative to resonate at a frequency in the first frequency band, and
wherein the second antenna branch and the second portion of the primary radiator are collectively operative to resonate at a frequency in the second frequency band.
16. A communication structure according to claim 15, wherein the first point on the primary radiator is arranged between the second point on the primary radiator and the ground point, and
wherein the first antenna port comprises a global positioning system (GPS) port.
17. A communication structure according to claim 16, wherein the second antenna port comprises a BlueTooth andor wireless local area network (WLAN) port.
18. A communication structure according to claim 16, wherein the second filter circuit comprises a second bandpass filter that is configured to provide a low ohmic path to signals corresponding to frequencies at least of about 2.4 GHz.