The Chengcheng vDisk compute sharing platform puts the PCs and GPUs in servers, labs, and research rooms into one resource pool and hands them out by time slot for remote use: server compute becomes virtual desktops, and lab PCs are published whole. No new equipment to buy; first put what you already have to use.
The first two figures are estimates under assumptions: a 60-PC lab with about 25 scheduled hours per week, opened for 53 hours across weekday evenings and weekends; actual results depend on the school's timetable and usage.
Well-equipped PCs in labs and research rooms spend most of their time waiting for the next class, while people who need compute queue up, pay out of pocket to rent cloud hosts, or are given high-end laptops
Each college and research group buys its own high-end workstations, fighting over them when in use and leaving them idle otherwise. Put into one pool and shared by time slot, the same demand needs fewer machines.
For graduation projects, competitions, and research that need temporary compute, borrow a lab PC with a discrete GPU first, with no need to rent cloud GPUs out of pocket.
Use the existing labs and deployed vDisk cloud desktops directly, with no rewiring of labs and no change to how classes run.
Professional software runs on the lab PC, and students connect from their dorm with the vDX client, using that lab PC's GPU.
Office and teaching software are fine on virtual desktops, starting from one Linux server; Intel integrated graphics can even be split across several virtual desktops.
Scheduled tasks in the console power machines on by time slot, borrowed machines are reclaimed on time, and slots nobody booked shut down on schedule.
Every remote connection is logged with time, computer, source address, and duration, so you can see whether the machines you opened up are actually being used.
Below is a simple estimate under a set of assumptions; actual results depend on the school's timetable and usage.
| Item | Estimate (assumptions) |
|---|---|
| Lab Scale | 60 PCs |
| Weekly teaching use | 30 scheduled class periods, about 22.5 hours, counted as 25 hours including changeovers |
| Weekly borrowed use (assumed) | Weekday evenings 6:00 PM to 11:00 PM, 25 hours in total; two weekend days 8:00 AM to 10:00 PM, 28 hours in total; 53 hours altogether |
| Overall utilization before opening up | 25 ÷ 168, about 15% |
| Overall utilization after opening up | (25 + 53) ÷ 168, about 46% |
| New usable machine-hours per week | 60 PCs × 53 hours = 3,180 machine-hours |
Server compute is published as virtual desktops and lab PCs are published whole; both kinds of desktop can go in the same desktop pool, or be assigned to the same person at once
The server's processors, memory, disks, and GPUs are published as virtual desktops by desktop pool: each pool sets the core count, memory, disk size, and GPU spec, machines are generated in bulk from a template, and the count can be raised or lowered at any time.
Physical lab terminals are published into desktop pools without a virtual machine: the system runs directly on that PC, and the person borrowing it has its processor, memory, GPU, and peripherals to themselves.
Intel integrated graphics can be split by desktop pool across several virtual desktops, handed out when one boots and taken back when it shuts down, with DirectX 12 and WebGL hardware-accelerated inside the desktops.
A desktop can be fixed to one person or made floating: assigned at sign-in, then restored automatically for the next person once returned. After a template update, publish the new version, and restore-mode desktops use it on their next boot.
Staff and students handle it themselves in the web portal, and the administrator only decides what is opened up and to whom
Teachers and students sign in to the web portal and book a virtual desktop or lab PC by time slot under "My bookings"; before booking they can see the upcoming slots when it is taken, conflicts are checked automatically on submit, and only one person can book the same machine in the same slot.
For the remote connection picture, network, data-out controls, and connection logs, seeRemote desktop publishing: VDI virtual desktops and physical desktops.
The same PC teaches by day and is borrowed after class; Windows and Linux, x86 and ARM64 all sit on one platform
One terminal can hold several systems: the teaching system for class and another environment for borrowing, chosen from the boot menu or set by timetable.
Physical terminals can publish Windows and Linux distributions such as Ubuntu, in bulk by group, or one at a time, or hidden.
Beyond x86, ARM64 platforms have been through adaptation testing and other platforms are adapted per model; ARM64 and LoongArch terminals run Linux systems.
The same system image can go straight to physical terminals or generate virtual desktops on the server; images for different processor architectures are made separately and managed together.
People who need compute use it after class, in the evenings, and over breaks, so machines have work to do outside the timetable
Design and computer science students use professional software in the lab remotely from their dorms in the evening, with no queue at the lab and no need to install large software on their own laptops.
Graduate students book lab PCs with a discrete GPU for model training, submit the job and disconnect, the PC keeps running, and the next day they check status in the mobile app and reconnect to see results.
Instructors book a batch of identically configured machines for a team, all using the competition environment, so they can practice evenings and weekends.
Labs are opened up for whole stretches over breaks, suited to multi-day simulation, rendering, and data processing.
Teachers use the workstation in their office or lab remotely from home, and can keep preparing lessons and processing data.
A few high-end workstations are booked by time slot and used in turns; office and document work goes on virtual desktops, so not everyone needs a high-end PC.
Chengcheng vDisk is anShanghai Chengcheng Information Technology Co., Ltd.in-house lab endpoint management platform with the engine, server, and endpoint ROM all built in-house and not based on Intel TCI; compute sharing and remote desktop publishing are new in vDisk6 on top of the cloud desktop and share one console with the lab cloud desktop.
vDisk cloud desktop is deployed in university labs including Shanghai Lixin University of Accounting and Finance (about 5,000 seats), Guizhou Light Industry Vocational University (about 3,000), Shanghai Publishing and Printing College (about 2,000), and Shanghai Jian Qiao University (about 800).
Know the prerequisites and limits first, so you can plan before opening up
The Chengcheng vDisk compute sharing platform puts the PCs and GPUs in servers, labs, and research rooms into one resource pool and hands them out by time slot for remote use: the server's processors, memory, disks, and GPUs are published as virtual desktops by desktop pool, and physical PCs in labs are published whole, using that PC's own processor, GPU, and peripherals. Both kinds of compute are published, booked, and managed in one platform.
Not necessarily. PCs already in labs can be published and borrowed by time slot, and labs with vDisk cloud desktops already deployed are included directly; to publish virtual desktops, one Linux server can both manage and run them. Put existing equipment to use first, then decide from usage records whether to add more.
Booking is by time slot, only one person can book the same PC in the same slot, and conflicts are checked automatically on submit; when the slot ends the PC is reclaimed automatically and any connected remote session is cut. Borrowing slots are set by the administrator outside class hours, and teaching labs still power on and off by timetable as usual.
They connect with the vDX client, which installs from Windows 7 up and launches with one click from the web page; virtual desktops can also be opened directly in a browser. Linux computers can install the vDX Linux client (x86, ARM64, LoongArch, and other architectures). When dorms and labs are on the same campus network, no public address is needed, and from off campus users can connect to the school VPN first.
Yes. Physical terminals can publish Ubuntu and other Linux distributions, x86 and ARM64 platforms have been through adaptation testing, and ARM64 and LoongArch terminals run Linux systems; the same system image can go to physical terminals or generate virtual desktops on the server.
Each connection logs the time, which desktop was connected, the source address, the duration, and the reason it ended, and live sessions can be cut on the spot; clipboard and file transfer switch on or off separately for in and out with optional size limits; the screen can carry a watermark, and people being monitored by an administrator are notified.
Related pages:Remote desktop publishing,Remote desktop publishing feature list,University Computer Lab Management,Linux VOI cloud desktop,How to manage 5,000 computers simultaneously
Pick one lab and one research group as a pilot, and we'll propose an opening plan based on your timetable and network