|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
1.
Test.zip (37 kB)
|
|
Issue Links:
|
Relate
|
|
|
|
This issue is related to:
|
|
CORE-1575
serious memory bug on multiple update a table in a single transaction
|
|
|
|
|
|
|
|
Look at the example
Start Transaction: isc_tpb_consistency,isc_tpb_no_auto_undo,isc_tpb_nowait
execute procedure TEST3
-----Statistics-----
Reads = 5344
Writes = 5053
Fetches = 8499490
Marks = 2810214
CurrentMemory = 17139964
MaxMemory = 17840520
NumBuffers = 1000
-----Detail statistics-----
read_seq_count
TEST_TABLE2 = 1000000
update_count
TEST_TABLE2 = 1000000
-----End------
execute procedure TEST3
-----Statistics-----
Reads = 12200
Writes = 495276
Fetches = 15811015
Marks = 5306902
CurrentMemory = 17140460
MaxMemory = 716093252
NumBuffers = 1000
-----Detail statistics-----
read_seq_count
TEST_TABLE2 = 1000000
update_count
TEST_TABLE2 = 1000000
-----End------
Commit Transaction
TEST3 is a simple procedure with the single update statement into it.
During the second call of TEST3 memory consumption grows extensively (see MaxMemory), exceeding database size at least five times more.
It seems, undo-log code needs for optimization.
With best regards, Eugene
|
|
Description
|
Look at the example
Start Transaction: isc_tpb_consistency,isc_tpb_no_auto_undo,isc_tpb_nowait
execute procedure TEST3
-----Statistics-----
Reads = 5344
Writes = 5053
Fetches = 8499490
Marks = 2810214
CurrentMemory = 17139964
MaxMemory = 17840520
NumBuffers = 1000
-----Detail statistics-----
read_seq_count
TEST_TABLE2 = 1000000
update_count
TEST_TABLE2 = 1000000
-----End------
execute procedure TEST3
-----Statistics-----
Reads = 12200
Writes = 495276
Fetches = 15811015
Marks = 5306902
CurrentMemory = 17140460
MaxMemory = 716093252
NumBuffers = 1000
-----Detail statistics-----
read_seq_count
TEST_TABLE2 = 1000000
update_count
TEST_TABLE2 = 1000000
-----End------
Commit Transaction
TEST3 is a simple procedure with the single update statement into it.
During the second call of TEST3 memory consumption grows extensively (see MaxMemory), exceeding database size at least five times more.
It seems, undo-log code needs for optimization.
With best regards, Eugene |
Show » |
|
Improvement
Minor
Avoiding excessive memory consumption by undo-log after series of updates 