- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for areas (0.02 sec)
-
src/packaging/common/packaging.properties
packaging.fess.heap.min=256m packaging.fess.heap.max=1g # Specifies the maximum file descriptor number packaging.os.max.open.files=65535 # Maximum number of VMA (Virtual Memory Areas) a process can own packaging.os.max.map.count=262144 # Simple marker to check that properties are correctly overridden packaging.type=tar.gz # Custom header for package scripts packaging.scripts.header=
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Dec 10 01:24:02 UTC 2015 - 797 bytes - Viewed (0) -
docs/tuning/tuned.conf
# Do not use swap at all vm.swappiness=0 vm.vfs_cache_pressure=50 # Start writeback at 3% memory vm.dirty_background_ratio=3 # Force writeback at 10% memory vm.dirty_ratio=10 # Quite a few memory map # areas may be consumed vm.max_map_count=524288 # Default is 500000 = 0.5ms kernel.sched_migration_cost_ns=5000000 # stalled hdd io threads kernel.hung_task_timeout_secs=85 # network tuning for bigger throughput
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Jul 12 23:31:18 UTC 2024 - 1.9K bytes - Viewed (0) -
src/packaging/deb/init.d/fess
LOG_DIR=${packaging.fess.log.dir} # Fess data directory DATA_DIR=${packaging.fess.var.dir} # Fess configuration directory CONF_DIR=${packaging.fess.conf.dir} # Maximum number of VMA (Virtual Memory Areas) a process can own MAX_MAP_COUNT=262144 # Path to the GC log file #FESS_GC_LOG_FILE=/var/log/fess/gc.log # Fess PID file directory PID_DIR=${packaging.fess.pid.dir}
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Sun Jan 15 06:32:15 UTC 2023 - 5.8K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
Including how to handle lifespan state that can be used in other areas of your code. /// ## Sub Applications { #sub-applications }
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 7.9K bytes - Viewed (0) -
docs/pt/docs/advanced/events.md
Incluindo como manipular estado do lifespan que pode ser usado em outras áreas do seu código. /// ## Sub Aplicações
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 8.5K bytes - Viewed (0) -
docs/es/docs/advanced/events.md
Incluyendo cómo manejar el estado de lifespan que puede ser usado en otras áreas de tu código. /// ## Sub Aplicaciones
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 8.2K bytes - Viewed (0) -
SECURITY.md
`SavedModel`) and executes them in parallel on available executors. Running TensorFlow in a multitenant design mixes the risks described above with the inherent ones from multitenant configurations. The primary areas of concern are tenant isolation, resource allocation, model sharing and hardware attacks. ### Tenant isolation Since any tenants or users providing models, graphs or checkpoints can execute
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Wed Oct 16 16:10:43 UTC 2024 - 9.6K bytes - Viewed (0) -
docs/es/docs/tutorial/background-tasks.md
# Tareas en Segundo Plano Puedes definir tareas en segundo plano para que se ejecuten *después* de devolver un response. Esto es útil para operaciones que necesitan ocurrir después de un request, pero para las que el cliente realmente no necesita esperar a que la operación termine antes de recibir el response. Esto incluye, por ejemplo: * Notificaciones por email enviadas después de realizar una acción:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 4.9K bytes - Viewed (0) -
CHANGELOG/OWNERS
- release-team-subproject-leads - satyampsoni # 1.32 Release Notes Lead reviewers: - release-managers - release-team-subproject-leads - satyampsoni # 1.32 Release Notes Lead labels: - sig/release
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Thu Dec 12 18:04:32 UTC 2024 - 417 bytes - Viewed (0) -
src/arena/arena.go
*/ package arena import ( "internal/reflectlite" "unsafe" ) // Arena represents a collection of Go values allocated and freed together. // Arenas are useful for improving efficiency as they may be freed back to // the runtime manually, though any memory obtained from freed arenas must // not be accessed once that happens. An Arena is automatically freed once // it is no longer referenced, so it must be kept alive (see runtime.KeepAlive)
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Wed Oct 12 20:23:36 UTC 2022 - 4.3K bytes - Viewed (0)