With the 9th week of GSoC gone, in this blog, we bring updates on what has been happening, with news from our mentors and contributors.
Updates from Veronica, our GSoC Admin and Mentor
Last week it was very challenging. We had to say goodbye to one of our contributors who could not continue working on the GSoC. A few months ago, in the GSoC Mentor Welcome Talk, we were briefed about various situations that could arise. It was one thing hearing it and another thing going through this. Communication is vital, and we kept everyone informed of all the steps being taken. However, it is still emotionally hard to go through some of these situations. Many of us were still on holiday breaks, so it was also a demanding week for the rest of us.
Updates from Daniel, our Slips Performance Contributor
This week, I wrapped up the live profiling implementation. I tested the implementation using a sample program and then integrated that into slips. I managed to work around the requirement of memray not being able to have multiple trackers running at once by utilizing a message queue to pass asynchronous start and stop requests to a controller process, which forwards start and stop signals to the other processes. I linked the other processes to the controller process by extending the multiprocess.Profile class and patching the class with a custom implementation with additional method calls. After working out some global variable/shared memory scope issues and testing with a smaller sample program, I integrated the code into slips and replaced the message queue interface with the existing redis database that slips uses. The vision for the live profiler is to have it linked to the web interface. Since the command “memray live <port>” must be run in the terminal to receive the profiling output, a way to have the browser access the local terminal and seamlessly display output that would normally be seen in the terminal is necessary. After the profiler is linked to the web interface, users should be able to toggle between processes they want to profile and see them displayed in the web interface. For the next week, I plan to do more testing to do with the profiler to make sure that everything is working fine after integration and to start working on a solution to link the terminal to the web interface, which can then display the profiler output.
Before you go…
In case you missed it, we have just released at Stratosphere a new tool called Collectress, designed to download external web threat intelligence feeds periodically and consistently. Read more.