모든 연결을 동시에. 중단된 지점부터 다시 시작.

유휴 연결 없음

GDM opens 8 connections by default, and you can set anything from 1 to 32 in Options → Connection. When a connection finishes its part, it takes over half of the largest part still left, so the work is shared out again and again until the file is done. A connection that falls far behind the others is dropped and opened again.

진행 창에는 전체 파일의 진행 상황과 각 연결의 시작 및 진행률을 보여주는 막대, 그리고 각 연결이 현재 무엇을 하고 있는지 보여주는 표가 실시간으로 그려집니다.

주장이 아닌 측정된 결과

On the same PC and the same test server, GDM fetched a 1 GiB file in 1.0 s against IDM 6.42's 5.5 s, and a 256 KiB file in 0.03 s against 3.1 s: the medians of alternating runs. The benchmark page has every run, the method and the raw data.

More connections help only where a server sends each one at a limited speed. Most servers allow a few connections per address, and GDM notices when one says no: it stops asking that server for more and lists what it learned under Exceptions in Options → Connection. You can set a number for a server yourself there too.

원한다면 32개 이상

옵션 → 연결에서 32개 이상의 연결 허용을 선택하면 다운로드당 최대 128개로 제한이 늘어나며, 서버 예외에도 적용됩니다. 명령줄의 -c는 1에서 128까지의 값을 가집니다.

충돌에도 살아남는 다시 시작

GDM saves how far each part has got as it goes. A download picks up where it stopped after you pause it, after the connection drops, or after Windows or GDM itself crashes. A connection that fails is retried on its own, and the table shows Retrying with the reason.

Before it continues, GDM checks that the file on the server is still the same one, so a changed file never gets stitched onto an old half. When a server can't send a file in parts, the progress window says Resume capability: No before you rely on it.

디스크로 바로 저장

Each connection writes directly into the file's place on disk, in a part file next to the final one. There is no temporary folder and no joining step at the end: when the last part arrives, GDM checks the size and renames the file.

손상된 다운로드 다시 시작은 링크가 만료되었을 때 어떻게 해야 하는지 보여줍니다.