[DiscordArchive] what year is it 1999 that we have single core cpus ?
[DiscordArchive] what year is it 1999 that we have single core cpus ?
Original source
what year is it 1999 that we have single core cpus ?
rektbyfaith
08-11-2025, 09:30 AM #1Archived author: Rymercyble • Posted: 2025-08-11T09:30:34.177000+00:00
Original source
what year is it 1999 that we have single core cpus ?
Original source
my pc hits 90c when compiling <:hyper_joy:376110808058429460>
rektbyfaith
08-11-2025, 09:30 AM #2Archived author: Mithria • Posted: 2025-08-11T09:30:37.010000+00:00
Original source
my pc hits 90c when compiling <:hyper_joy:376110808058429460>
Original source
well, on a full compile
rektbyfaith
08-11-2025, 09:31 AM #3Archived author: Mithria • Posted: 2025-08-11T09:31:01.030000+00:00
Original source
well, on a full compile
Original source
A compile can use 100% of all cores, it makes sense that having the worldserver running at the same thing can impact performance. A response will this is in my opinion not appropriate.
rektbyfaith
08-11-2025, 10:49 AM #4Archived author: Revision • Posted: 2025-08-11T10:49:39.672000+00:00
Original source
A compile can use 100% of all cores, it makes sense that having the worldserver running at the same thing can impact performance. A response will this is in my opinion not appropriate.
Original source
compile will use exactly how many cores you assign to it
rektbyfaith
08-11-2025, 10:51 AM #5Archived author: Rymercyble • Posted: 2025-08-11T10:51:00.938000+00:00
Original source
compile will use exactly how many cores you assign to it
Original source
And most people don't have that many cores, 4 isn't entirely uncommon. Even if they have the cores for it they usually don't have the RAM for compiling with that many anyway.
rektbyfaith
08-11-2025, 10:51 AM #6Archived author: Revision • Posted: 2025-08-11T10:51:21.962000+00:00
Original source
And most people don't have that many cores, 4 isn't entirely uncommon. Even if they have the cores for it they usually don't have the RAM for compiling with that many anyway.
Original source
Yes, tell users on Windows to assign the number of cores and then spend hours trying to coach them through that.
rektbyfaith
08-11-2025, 10:51 AM #7Archived author: Revision • Posted: 2025-08-11T10:51:45.119000+00:00
Original source
Yes, tell users on Windows to assign the number of cores and then spend hours trying to coach them through that.
Original source
I personally rather have worldserver down and give it access to all cores to make the process faster than limit the number of cores to compile. 30 minutes to compile on the low-end of a 4-core CPU isn't a long time.
rektbyfaith
08-11-2025, 10:53 AM #8Archived author: Revision • Posted: 2025-08-11T10:53:29.955000+00:00
Original source
I personally rather have worldserver down and give it access to all cores to make the process faster than limit the number of cores to compile. 30 minutes to compile on the low-end of a 4-core CPU isn't a long time.
Original source
Its actually mostly not about downtime because of compiling, but to reduce duplications of files and effort.
The idea was to prep and build the server, make sure it runs and then just simply copy over the compiled stuff to "live" so it will update itself with the next startup.
Keeping two copies of the git repos and build folders, one for "dev" and one for "live" was something i wanted to avoid just because ease of use.
Therefore the original question
what data from the source and build folder is used by the worldserver?
Since then i could just make a copy of those specific files and copy them over to the "live" directory when doing a release.
Maybe thats overcomplicating things - thats why I asked how others do it
rektbyfaith
08-11-2025, 11:12 AM #9Archived author: Tecc • Posted: 2025-08-11T11:12:58.974000+00:00
Original source
Its actually mostly not about downtime because of compiling, but to reduce duplications of files and effort.
The idea was to prep and build the server, make sure it runs and then just simply copy over the compiled stuff to "live" so it will update itself with the next startup.
Keeping two copies of the git repos and build folders, one for "dev" and one for "live" was something i wanted to avoid just because ease of use.
Therefore the original question
what data from the source and build folder is used by the worldserver?
Since then i could just make a copy of those specific files and copy them over to the "live" directory when doing a release.
Maybe thats overcomplicating things - thats why I asked how others do it
Original source
On Linux you don't have to do any of that. If you make install and then restart worldserver it'll automatically update. I don't know if you're on Windows though which makes it a different matter. Personally I just shut the servers down and update them and then boot it back up. I understand some don't want to do that and that's ok, doing what you're doing seems like the reasonable way of doing it in that case I think.
rektbyfaith
08-11-2025, 11:21 AM #10Archived author: Revision • Posted: 2025-08-11T11:21:50.774000+00:00
Original source
On Linux you don't have to do any of that. If you make install and then restart worldserver it'll automatically update. I don't know if you're on Windows though which makes it a different matter. Personally I just shut the servers down and update them and then boot it back up. I understand some don't want to do that and that's ok, doing what you're doing seems like the reasonable way of doing it in that case I think.