Hi Ratnadeep, I briefly went through the test cases you provided however I am not sure how these test cases test the asterixdb parameters as part of its system? I could not see how any of the classes and parameters from AsterixDB are tested, they were mainly defined by your code as far as I could see, but Ian can verify that.
Also I think the deadline for your proposal is fast approaching (March 28th I think). If you want to get a better idea of the project maybe briefly go through this thesis:( https://scholarcommons.scu.edu/cgi/viewcontent.cgi?params=/context/cseng_mstr/article/1034/&path_info=Giulliano_Silva_Zanotti_Siviero_Thesis.pdf ). Let me know if you have any questions. Best, On Sat, Mar 21, 2026 at 7:57 AM Ratnadeep Mohanta < [email protected]> wrote: > Dear Mentors, > > I hope you are doing well. > > I wanted to share an update regarding my progress with the AsterixDB > codebase. I have successfully set up the project locally and explored its > existing functionality. As part of understanding the system and preparing > for further contributions, I have implemented and executed several tests on > the Asterix side. > > The tests I worked on include: > > 1. > > Integration Tests > 2. > > Unit Tests > 3. > > Query Tests > 4. > > Configuration Tests > 5. > > Capacity/Resource Tests > > These tests were designed to evaluate different aspects of the current > system behavior and to build a stronger understanding of how AsterixDB > handles execution, configuration, and resource management. > > I have pushed my work to my GitHub repository, and you can review it here: > https://github.com/RatnadeepCode/asterixdb/tree/memory-improvement > > I would really appreciate any feedback or suggestions on the tests or > overall approach. I am looking forward to improving further and > contributing more meaningfully to the project. > > Thank you for your time. > > Best regards, > Ratnadeep Mohanta > > > > On Tue, Mar 3, 2026 at 1:37 AM Ian Maxon <[email protected]> wrote: > > > Hi Ratnadeep, > > Thanks for your interest in the topic. I would look first at > > JobCapacityController, and give the Hyracks > > paper(https://asterix.ics.uci.edu/pub/Hyracks.pdf) a read to get a > > general sense of the broad memory constraints and controls for each > > Hyracks job. Then, you can look at SetMemoryRequirementsRule to see > > how Asterix is currently calculating the required memory for a job > > during compile time (the compiled form of a query) > > > > A good first contribution towards this topic might be some more tests > > on the Asterix side regarding the current functionality. There are > > some tests in Hyracks for the CapacityController, but to my knowledge > > there aren't many that check the behavior of the parameters that are > > used on the Asterix side. > > > > Thanks, > > - Ian > > > > On Mon, Mar 2, 2026 at 11:14 AM Ratnadeep Mohanta > > <[email protected]> wrote: > > > > > > Hi everyone, > > > > > > I’m Ratnadeep from India, currently a B.Tech CSE student at Amity > > > University. I have been programming for around two years and have > worked > > > with languages such as C, C++, and Java. I am also currently working in > > web > > > development and have experience building full-stack websites. > > > > > > I’ve recently started exploring the dynamic memory management idea in > > > Apache AsterixDB, particularly around improving the current static > > > budgeting approach for memory-intensive operators. I’ve begun going > > through > > > the documentation and relevant parts of the codebase to understand how > > > operator memory is currently allocated and managed. > > > > > > I’m very interested in contributing further in this area and would > really > > > appreciate guidance on what I can work on next to make meaningful > > > contributions. Are there specific components, issues, or discussions I > > > should focus on? > > > > > > Thanks, > > > Ratnadeep > > > -- Shiva Jahangiri Assistant Professor in Computer Science and Engineering Department Santa Clara University
