vieter-v/vieter
vieter-v/vieter
Archived
2
1
Fork 5
Code Issues 84 Pull requests 4 Projects Releases 12 Packages 1 Wiki Activity

Investigate memory usage #122

New issue
Closed
opened 2022-04-10 10:34:09 +02:00 by Jef Roosens · 3 comments
Jef Roosens commented 2022-04-10 10:34:09 +02:00
Owner
Copy link

It seems that when the builders are uploading big packages, the RAM usage of the Vieter server itself also goes up drastically. This could potentionally become an issue, so it must be investigated further.

It seems that when the builders are uploading big packages, the RAM usage of the Vieter server itself also goes up drastically. This could potentionally become an issue, so it must be investigated further.
Jef Roosens added this to the 0.3.0 milestone 2022-04-10 10:34:09 +02:00
Jef Roosens commented 2022-04-10 10:52:19 +02:00
Author
Owner
Copy link

After some testing, it seems that Vieter does indeed try to load entire archives into memory, which is honestly quite surprising.

After some testing, it seems that Vieter does indeed try to load entire archives into memory, which is honestly quite surprising.
Jef Roosens commented 2022-04-10 11:04:38 +02:00
Author
Owner
Copy link

Annoyingly enough, this increase in memory usage does not seem to happen when testing locally.

Annoyingly enough, this increase in memory usage does not seem to happen when testing locally.
Jef Roosens modified the milestone from 0.3.0 to 0.4.0 2022-04-20 09:56:36 +02:00
Jef Roosens modified the milestone from 0.4.0 to (deleted) 2022-04-20 09:57:43 +02:00
Jef Roosens commented 2022-05-20 20:13:34 +02:00
Author
Owner
Copy link

This is a non-issue. The memory increase is caching of the kernel, it doesn't actually take away memory from other programs.

This is a non-issue. The memory increase is caching of the kernel, it doesn't actually take away memory from other programs.
This repository is archived. You cannot comment on issues.
No Branch/Tag specified
Branches Tags
dev
renovate/nokogiri-1.x
renovate/redcarpet-3.x
renovate/busybox-1.x
main
release-0.6.0
0.6.0
0.5.0
0.5.0-rc.2
0.5.0-rc.1
0.4.0
0.3.0
0.3.0-rc.1
0.3.0-alpha.2
0.3.0-alpha.1
0.2.0
0.1.0
0.1.0-rc1
Labels
Clear labels   
Roadmap

Tracking issue for a larger task

  
V

This issue is blocked by a V issue

  
bug

Something is not working

  
docs

Something to add to the documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
good first issue

A good issue to start out with as a new contributor

  
help wanted

Need some help

  
idea

Issue for brainstorming a new idea

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

  
Idea

Issue for brainstorming a new idea

  
Roadmap

Tracking issue for a larger task

  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#122
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?