Skip to content

Commit

Permalink
Docs(meeting notes) update documentation of week-05 meeting.
Browse files Browse the repository at this point in the history
  • Loading branch information
Aaditya-Singh78 committed Jul 6, 2024
1 parent 9c22afb commit de304d1
Show file tree
Hide file tree
Showing 3 changed files with 119 additions and 0 deletions.
Binary file added docs/2024/scheduler/asset/arch_ver.02.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
63 changes: 63 additions & 0 deletions docs/2024/scheduler/updates/2024-06-06.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: Weekly Updates (Community Bonding)
author: Aaditya Singh
---
<!--
SPDX-License-Identifier: CC-BY-SA-4.0
SPDX-FileCopyrightText: 2024 Aaditya Singh <[email protected]>
-->

# Meeting 7

*(June 06, 2024)*

## Attendees

- [Katharina Ettinger](https://github.com/EttingerK)
- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
- [Kaushlendra Pratap](https://github.com/Kaushl2208)
- [Ayush Bhardwaj](https://github.com/hastagAB)
- [Abdelrahman Jamal](https://github.com/Hero2323)
- [Aaditya Singh](https://github.com/Aaditya-Singh78)
- [Akash Sah](https://github.com/Akashsah2003)
- [Divij Sharma](https://github.com/dvjsharma)
- [Rajul Jha](https://github.com/rajuljha)
- [Avinal Kumar](https://github.com/avinal)
- [Vasudev Maduri](https://github.com/vasudevmaduri)
- [Shreya Gautam](https://github.com/ShreyaGautamm)

## Missed

- [Samuel Dushimimana](https://github.com/dushimsam)
- [Gaurav Mishra](https://github.com/GMishx)
- [Soham Banerjee](https://github.com/soham4abc)
- [Shreya Singh](https://github.com/SinghShreya05)
- [Abhishek Kumar](https://github.com/abhi-kumar17871)
- [Valens Niyonsenga](https://github.com/valens200)
- [Anupam Ghosh](https://github.com/ag4ums)
- [Sahil Jha](mailto:[email protected])

## General Discussion

**Mentors:**

- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd): Provided general updates about the project.
- [Avinal Kumar](https://github.com/avinal): Suggested using a tool like [LanguageTool](https://languagetool.org) for creating GSoC documentation.

**Contributors**:

- [Abdelrahman Jamal](https://github.com/Hero2323): Demonstrated a short demo on current work involving parsing comment text of a file from FOSSology, prompting it to multiple LLM's for license name recognition. Mentioned the need to clean up and reorder the data.

- [Shreya Gautam](https://github.com/ShreyaGautamm): Presented a PPT on the end-to-end flow and code of the Safaa project, currently working on scripts to extract data from FOSSology.

- [Aaditya Singh](https://github.com/Aaditya-Singh78): Discussed rewriting the scheduler code from C to Go based on last meeting with mentors, raised a PR for the same. Exploring different approaches to complete this task.

- [Abhishek Kumar](https://github.com/abhi-kumar17871): Was absent.

- [Akash Sah](https://github.com/Akashsah2003): Discussed with mentors about using JSON format to convert the license expression and store it in a database, currently working on creating a UI for the same.

- [Divij Sharma](https://github.com/dvjsharma): Completed implementation of OAuth via API; currently looking into upgrading API from V1 to V2.

- [Rajul Jha](https://github.com/rajuljha): Discussed pulling line numbers of findings and integration challenges, was able to fetch keyword information but faced issues with copyright.

- [Valens Niyonsenga](https://github.com/valens200): Was absent.
56 changes: 56 additions & 0 deletions docs/2024/scheduler/updates/2024-06-07.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
title: OVERHAULING SCHEDULER DESIGN (Discussion)
author: Aaditya Singh
---
<!--
SPDX-License-Identifier: CC-BY-SA-4.0
SPDX-FileCopyrightText: 2024 Aaditya Singh <[email protected]>
-->

# Meeting 8

*(June 07, 2024)*

## Attendees

- [Katharina Ettinger](https://github.com/EttingerK)
- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
- [Gaurav Mishra](https://github.com/GMishx)
- [Kaushlendra Pratap](https://github.com/Kaushl2208)
- [Avinal](https://github.com/avinal)
- [Aaditya Singh](https://github.com/Aaditya-Singh78)

## Discussion

**Contributors**:

- [Aaditya Singh](https://github.com/Aaditya-Singh78): Discussing integration and implementation strategies for the new scheduler design.

![architecture-version: 02](../asset/arch_ver.02.png)

It consists of a sophisticated job scheduling system that leverages Go's powerful concurrency features to efficiently manage tasks across two *primary queues*:

1. Dependent Queue
2. Independent Queue

Each queue is managed by a dedicated Global Go-Routine, which orchestrates the distribution and execution of tasks among multiple subordinate Go-Routines. These Go-Routines operate in parallel, each managing its own set of threads to ensure tasks are executed concurrently, *maximising throughput* & *minimising response time*.

**Key Components:**

- *Database*: Central storage for all job-related data, ensuring durability and consistency across job executions.

- *Dependent Queue*: Manages jobs that depend on the completion of other jobs, ensuring correct execution order.

- *Independent Queue*: Handles jobs that can be executed independently, allowing for simultaneous processing and improved efficiency.

- *Logging*: Each thread incorporates logging to track job execution, facilitating debugging and system monitoring.

- *Termination*: Ensures all tasks are either completed or properly terminated before system shutdown, maintaining system integrity.

**Mentors**:

- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd): Questioned whether priority can be implemented in both dependent and independent queues effectively.

- [Gaurav Mishra](https://github.com/GMishx): Highlighted considerations for ensuring mutual exclusivity either across dependent or independent queues, with a focus on execution rules and limitations.

- [Kaushlendra Pratap](https://github.com/Kaushl2208): Inquired about how goroutines can achieve both concurrency and parallelism, and whether they should operate synchronously or asynchronously.

0 comments on commit de304d1

Please sign in to comment.