Back to the 70's , the shared computer age

A forum for topics that don't fit elsewhere. Introduce yourselves to other members of the forums, discuss how your name evolves when written out in the Game of Life, or just tell us how you found it. Forum rules still apply.
Post Reply
Dylan Chen
Posts: 116
Joined: March 27th, 2020, 8:07 am

Back to the 70's , the shared computer age

Post by Dylan Chen »

In 70's, computer using are shared by a bunch of people. You have to make appointment before get access to the precious computer.

Untill the popularity of personal computer, Life enthusiasts can do the computing at home.

The highly efficiency and accessibility of cloud computing makes me wondering, do we renaissance to the "shared computer age" again?
Tools should not be the limit.
Whether your obstacle is a script, an stdin, or Linux environment computing resouces.
check New rules thread for help.
Dylan Chen
Posts: 116
Joined: March 27th, 2020, 8:07 am

Re: Back to the 70's , the shared computer age

Post by Dylan Chen »

The instance type I used includes:

1. Cluster of 70 core1, running apgsearch C1, submitting hauls with a unique suffix of soups number. It is manipulated via built-in bash script, so you don't need to config each of them respectivly.

2. Several V100 GPU instance with core12. I run it with apgsearch G1, get a performance of 1.1-1.14 mi soups/s.

3. Some core24 instance machine. I have tried LSSS and ikpx2 on them. result was good.
Discord citation: apgoucher12/25/2020
@inspirehep found a new p660 puffer.(it is actually not a new discovery, but it does the first in ikpx2-Catagolue)
Tools should not be the limit.
Whether your obstacle is a script, an stdin, or Linux environment computing resouces.
check New rules thread for help.
Dylan Chen
Posts: 116
Joined: March 27th, 2020, 8:07 am

Re: Back to the 70's , the shared computer age

Post by Dylan Chen »

Convenience of cloud computing. you can access your computing via phone

The connecting method of cloud instance is SSH mainly, some of the cloud provider also have webpage Workbench or sth.
that means you can easily access the computing any where and any time. any devices have a browser could view and inspect your cloud instance easily.

it has pre-built-in computing evironment. any distribution of Linux, any packages you want, the latest Cuda environment. You don't have to setup those things every time.
Tools should not be the limit.
Whether your obstacle is a script, an stdin, or Linux environment computing resouces.
check New rules thread for help.
MathAndCode
Posts: 5285
Joined: August 31st, 2020, 5:58 pm

Re: Back to the 70's , the shared computer age

Post by MathAndCode »

Are you trying to propose some sort of shared account where Lifeenthusiasts can create, edit, and save partials that others can access and complete without having to bother posting each individual partial?
I am tentatively considering myself back.
Dylan Chen
Posts: 116
Joined: March 27th, 2020, 8:07 am

Re: Back to the 70's , the shared computer age

Post by Dylan Chen »

MathAndCode wrote: December 28th, 2020, 12:48 am Are you trying to propose some sort of shared account where Lifeenthusiasts can create, edit, and save partials that others can access and complete without having to bother posting each individual partial?

1.no, just some personal experience about the devolopment of cloud computing. my thought didn't go that further .

2.yes, this "co-working" idea is excellent. it avoid many overlap on the same work and is more friendly to beginners.

3.current wiki page and discord discuss channel works fine, except not that seamless and universal
Tools should not be the limit.
Whether your obstacle is a script, an stdin, or Linux environment computing resouces.
check New rules thread for help.
Dylan Chen
Posts: 116
Joined: March 27th, 2020, 8:07 am

Re: Back to the 70's , the shared computer age

Post by Dylan Chen »

for beginners who don't familiar with Unix, here is some tips when performing search.

1.you can let the program backup the output to a text file.
e.g.(calcyman|discord)

Code: Select all

If you're running a non-interactive search program, you don't need screen; for example, you can run:
./ikpx2 [arguments] | tee -i progress.txt &disown

The tee command saves the progress, and the &disown makes the program run in the background and survive when you disconnect. slight_smile
2. If you run with a remote computer (cloud or sth), the command would stop when you disconnect. Using screen or nohup.

Code: Select all

screen ./apgluxe -n 100000
3. There also other way to store the output properly.

Code: Select all

./ntzfind (parameters) | tee (Your File) #should put it both on the screen and in a file
#Ampere
Or use ">"
SomeCommand > SomeFile.txt
./ntzfind > output2021.txt
Attachments
Screenshot_2021-01-02-09-58-34-935_com.discord.jpg
Screenshot_2021-01-02-09-58-34-935_com.discord.jpg (578.73 KiB) Viewed 1161 times
IMG_20210102_093929.jpg
IMG_20210102_093929.jpg (122.92 KiB) Viewed 1161 times
Tools should not be the limit.
Whether your obstacle is a script, an stdin, or Linux environment computing resouces.
check New rules thread for help.
Post Reply