>107416103
Is slot id a lottery? Can I choose which slot to start with at server's start? This was a fresh start, and keeps picking id3 which I do not know BEFORE I start processing some prompt. But I want to load a pre-caches one
slot get_availabl: id 3 | task -1 | selected slot by LRU, t_last = -1
slot launch_slot_: id 3 | task -1 | sampler chain: logits -> logit-bias -> penalties -> dry -> top-n-sigma -> top-k -> typical -> top-p -> min-p -> xtc -> temp-ext -> dist
slot launch_slot_: id 3 | task 1 | processing task
slot update_slots: id 3 | task 1 | new prompt, n_ctx_slot = 131072, n_keep = 0, task.n_tokens = 289
slot update_slots: id 3 | task 1 | n_tokens = 0, memory_seq_rm [0, end)
slot update_slots: id 3 | task 1 | prompt processing progress, n_tokens = 225, batch.n_tokens = 225, progress = 0.778547
slot update_slots: id 3 | task 1 | n_tokens = 225, memory_seq_rm [225, end)
slot update_slots: id 3 | task 1 | prompt processing progress, n_tokens = 289, batch.n_tokens = 64, progress = 1.000000
slot update_slots: id 3 | task 1 | prompt done, n_tokens = 289, batch.n_tokens = 64
slot update_slots: id 3 | task 1 | created context checkpoint 1 of 8 (pos_min = 224, pos_max = 224, size = 75.376 MiB)
srv log_server_r: request: GET /props 127.0.0.1 200
srv log_server_r: request: GET /slots 127.0.0.1 200
srv log_server_r: request: GET /slots 127.0.0.1 200
srv log_server_r: request: GET /slots 127.0.0.1 200
srv log_server_r: request: POST /v1/chat/completions 127.0.0.1 200
srv stop: cancel task, id_task = 1
slot release: id 3 | task 1 | stop processing: n_tokens = 470, truncated = 0
srv update_slots: all slots are idle