![]() If you configure too many ASE engines for the underlying CPU’s, you will observe some significant loss of throughput. Whether you bring them all online at startup or not depends on what else is running on the system and the specific workload you have on this server. So I’d always recommend setting it to the total number of logical CPU’s or this number minus 1. Increasing the max number of online engines to higher number than the number of available logical CPU’s makes no sense. You can also set the second one to a lower value and benchmark the system with less engines and then bring one additional engine online after another. The first line defines that there will be 3 engines and the second one that all 3 engines will be started by default.Įven though in many cases, it makes sense to set the same value to both parameters so that you automatically use all available engines. ![]() You can change this setting also in the SYBASE.cfg: So assuming you have a dedicated server with 4 CPU cores, you’ll want to configure 3 engines. Usually, if you server is almost exclusively used for ASE and you have X CPU cores available, you will want to configure X-1 engines. (replace N by the number of engines you want to configure). You can change the number of engines by using the following command: sp_configure "engine", N $query = 'FOR p IN PATHS(vertices_20130301_01, edges_20130301_01, "outbound")įILTER p.source._id = "vertices_20130301_01/v4"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |