similar to: memory consumption with treesize pro and cifs shares

Si, Carlos. Yo hago lo mismo, pero esos mismos numeritos salen enormes. > treesize(RFfit) [1] 4304 4302 4311 4319 4343 4298 4298 4311 4349 4327 4331 4317 4294 4321 4283 4362 [17] 4300 4330 4266 4331 4308 4352 4294 4315 4372 4349 4331 4347 4329 4348 4298 4335 [33] 4346 4396 4345 4313 4293 4276 4353 4272 4304 4325 4317 4336 4308 4351 4374 4324 [49] 4386 4359 4311 4346 4300

Gracias Carlos y Javier, ntrees es el nº de árboles y treesize sus respectivos tamaños (nº de nodos) ntree: Number of trees to grow. This should not be set to too small ...... treesize: Size of trees (number of nodes) in and ensemble. Puse 1000 árboles (ntree=1000), si, pero la función treesize te da el nº de nodos: treesize(RFfit, terminal=TRUE) me da un vector de 1000 elementos (uno

Muchas gracias Carlos, como siempre. Es raro que se me pasase. En su momento miré todos los argumentos del RF, como hago siempre, pero ese lo había olvidado. La verdad es que funcionaba estupendamente, pero me parecía extraño. Aunque dado que los RF no sobreajustan, no hay problema con que sus árboles sean todo lo grandes que quieras. Lo he testado con una base de datos externa y explica

Buenas tardes a todos. El paquete randomForest tiene la función treesize, que es el nº de nodos. Me dan valores realmente elevados (en torno a 1000), y eso me parece extraño. ¿sabéis si es así? Gracias, Manuel -- Dr Manuel Mendoza Department of Biogeography and Global Change National Museum of Natural History (MNCN) Spanish Scientific Council (CSIC) C/ Serrano 115bis, 28006 MADRID Spain

Buenas. El Paquete pdp es muy fácil de usar, pero cuando se lo aplico a mis datos me da: Error in eval(stats::getCall(object)$data) : object 'x.data' not found. Os copio abajo un ejemplo de aplicación a un RF. El mio es de un boosted regression trees (paquete gbm). No sé si esa puede ser la razón del error. En el paquete pdp no especifica que sea solo para RF, aunque en los

Hello, I?m running TrueNAS 24.10.2.2, which uses Samba 4.20.5-truenas. I have a mixture of Mac, Linux, and Windows SMB clients in my network that talk to the TrueNAS server over SMB. Apologies in advance for the slightly long-winded setup to my question; I wanted to explain how I got here. I?d like to be able to use Server-Side Copy (SSC) (https://wiki.samba.org/index.php/Server-Side_Copy)

There are two styles of SSC: - the "normal" protocol style called copy-chunk, where the copy is requested in IO ranges by the client and performed server-side - the Apple way enabled by fruit:copyfile where the client requests the *whole* file to be copied in one request to be performed by the server The problem with the latter is that for large file the copy takes some time and

I have a Cyber Power LE1000DG UPS I got from Best Buy this weekend. I plan to use it with a TrueNAS scale system, and it is connected via USB. Vendor link: https://www.cyberpowersystems.com/product/ups/battery-backup/le1000dg/. TrueNAS has you pick a UPS driver. I could not find any "LE" related models on https://networkupstools.org/stable-hcl.html (which is the list TrueNAS uses). Per

I have a Smart-UPS RT 3000 XL connected via serial cable to TrueNAS TrueNAS-9.2.1.2-RELEASE-x64 (002022c) which runs on FreeBSD 9.2-RELEASE-p3. When I start the NUT service, I get the message: Oct 20 01:53:50 truenas notifier: very old or unknown APC model, support will be limited Which I interpret as an indicator of less than optimal operating mode. I suspect that the model identifier is not

Really nice write-up on the Samba-based Open Source project ! https://arstechnica.com/gadgets/2020/07/an-easy-mode-for-zfs-we-test-the-truenas-core-12-0-beta/ Congratulations to the FreeNAS/TrueNAS folks ! Jeremy.

On Fri, 17 Jan 2025 22:32:03 +0100 Carlos Alberto Balseiro Mayi via samba <samba at lists.samba.org> wrote: > ? > HI everyone. > > I've been analyzing a problem with an embedded Linux/FPGA device that > in some cases was failing to run properly when using files from a > samba share. After some time I've found it is related to Samba bug > 12783 and setting

These are a combination of "temp" and "real" files. The user is deleting/moving PDFs, InDesign and image files. I'm presuming hidden files are also getting deleted when the real files are. The filesystem has been solid (XFS) up until the switch to SMB. From: itdept_head <itdept_head at grown-up.com> To: Cc: "samba at lists.samba.org" <samba at

? HI everyone. I've been analyzing a problem with an embedded Linux/FPGA device that in some cases was failing to run properly when using files from a samba share. After some time I've found it is related to Samba bug 12783 and setting kernel oplocks on global fix the issue. But while looking at that I have found a strange behavior I can't understand. I have guest ok = yes on the

That isn't how rsync should work with -a. Is something preventing it from backdating the file? What is the filesystem? Can you try copying your 2015 file with cp -a? On 10/9/24 14:56, McDowell, Blake wrote: > Hi Kevin, > > The -a flag in this instance is not back-dating the timestamp of the > copied file to the source file. It is modifying it to the time of > transfer

Hi I have a bunch of FreeNAS servers and a TrueNAS HA server all spamming the logs with these messages every minute about their own source name (examples below). These boxes are on two physically separate networks, and I find it unlikely both networks should have some sort of undetected loop. Any ideas on how to debug this? Samba version is 4.1.18. FreeNAS box on network A " Jan 5

Hello, I have a question about how/why rsync updates modification times, which I haven?t been able to find an answer to. I have two locally connected storage devices running TrueNAS Core: one is new and empty, while the other is filled with files. When I run the following rsync command: rsync -avPh --itemize-changes --stats "${@}" to transfer files from the full storage to the empty

Thanks a lot for your analysis. I just wanted to add that I think we are not using at all? The client is an embedded Linux/FPGA machine and it doesn't have mount.cifs . I think it is using https://wiki.samba.org/index.php/LinuxCIFSKernel . It comes default with kernel 5.15 but I tried with a 6.10 and same problem happens. Best Regards, Carlos A. Balseiro El 2025-01-18 11:32, Rowland

Heya, first time posting to a mailing list so please excuse me if I do something wrong :) I'm new to NUT and trying to get things working on my TrueNAS, I have a "Vultech 1500VA" UPS which comes with the software "PowerManager II" and it seems to be using the "richcomm_usb" driver. There are 5 devices in the compatibility list and I tried all of them, sadly to

Hi all, A few questions. - Is POSIX locking enabled when using the native client? I would assume yes. - What other settings/tuneables exist when it comes to file locking? Krist -- Vriendelijke Groet | Best Regards | Freundliche Gr??e | Cordialement ------------------------------ Krist van Besien | Senior Architect | Red Hat EMEA Cloud Practice | RHCE | RHCSA Open Stack @: krist at

You are using rsync -a which copies (preserves) the timestamp. Meaning that rsync will copy the file then back-date it to the timestamp of the source file. Most copying tools do not do this though cp's -a does it too. Note that your itemized output says that the timestamp is different meaning that the file has changed since rsync last ran. Without the -a (or the included -t) the