We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
db2 luw restore to avoid O_SYNC writes on the tablespace containers and perform a final fsync()
db2 luw restore performance is very slow. The problem was identified and recommended solution is to avoid O_SYNC writes on the tablespace containers and perform a final fsync()
From: David Sciaraffa Date: Tuesday, February 27, 2018 at 6:57 PM To: Raj Merchia Cc: "Inala, Aravind" , Biswarup Mukherjee , Christopher Tsounis , Dale McInnis/Toronto/IBM , Dave Ziony , Hemanth Thota , Scott Maberry , Vinod Machcharla Subject: Re: Visa - Restore performance on 100TB database (Case TS000107666) Raj, thanks for sharing. The feedback I received from our Db2 memory architect had similar detail about how GPFS utilizes its buffer pool and not the filesystem cache.
I'm gaining more confidence that it will be possible to move forward with prototyping a method for Restore to avoid O_SYNC writes on the tablespace containers and perform a final fsync() at the end. This is not at the top of our domain's priorities at the moment, but I'll try to squeeze in some time to prototype it soon. I cannot provide you with an ETA yet.
Thanks, ------------------------------------------------------------ David Sciaraffa, Development Manager, Db2 Availability email@example.com, 905-413-4037 IBM Toronto Development Lab, C4/152/8200/MKM
Do not place IBM confidential, company confidential, or personal information into any field.