IQSS logo

IRC log for #dataverse, 2018-04-19

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
03:02 jri joined #dataverse
07:21 jri joined #dataverse
07:27 jri joined #dataverse
10:52 donsizemore joined #dataverse
13:58 donsizemore joined #dataverse
14:19 pameyer joined #dataverse
14:40 pameyer pdurbin: thanks for less xhtml on API errors :)
14:45 pdurbin sure, I'm writing a comment on https://github.com/IQSS/dataverse/issues/4396 now. how to test, etc
14:49 pdurbin pameyer: ok, please take a look and add more if I'm forgetting anything important.
14:51 pameyer will do
14:52 pameyer and thanks for updating with develop
14:53 pdurbin Sure, there were minor merge conflicts. I had added new methods in UtilIT in the same place. Not a big deal.
15:03 donsizemore joined #dataverse
15:07 pameyer pdurbin: don't see anything to add to your notes there
15:07 Thali_UM joined #dataverse
15:08 Thali_UM Hi Philip
15:08 Thali_UM In what is Dataverse programmed?
15:08 Thali_UM Good morning
15:13 pameyer morning Thali_UM: are you wondering about programming language, framework, OS, tools?
15:13 Thali_UM All
15:14 Thali_UM Language programming is JAVA?
15:14 pameyer java , JSF / primefaces / a bunch of java ecosystem stuff I don't understand well enough , dev on OS X for deployment on linux
15:14 pameyer I use vim/maven for dev tools, but most of the iqss team usees netbeans
15:14 Thali_UM is a tools primefaces?
15:15 pameyer primefaces is used to generate the web UI - it's a java library (or framework)
15:15 Thali_UM Good morning pameyer
15:16 Thali_UM Ok
15:16 pameyer JSF and primefaces interact in ways that pdurbin would be better able to answer than me ;)
15:17 Thali_UM Thank you for the answere Pameyer
15:17 Thali_UM What tool do they use to document?
15:19 pameyer the guides are written in restructured text, which is processed by sphinx
15:20 pameyer there's some javadoc style comments in the source code, but my impression is that those aren't used very often
15:21 pdurbin Thali_UM: good morning. Please see http://guides.dataverse.org/en/4.8.6/developers/intro.html#core-technologies
15:23 Thali_UM Yes Philip
15:23 Thali_UM Thank you Pameter and Philip
15:29 pameyer glad to help
15:44 pdurbin every lab should have a pameter ;)
15:45 pdurbin Thali_UM: you can read more about our use of Sphinx at http://guides.dataverse.org/en/4.8.6/developers/documentation.html
15:46 Thali_UM Oooohhhh
15:46 Thali_UM Thank you Philip
15:48 pdurbin pameyer: I can't decide if it's valuable to build and host an HTML version of the javadoc or not. I can kick off a build if you'd like.
15:50 pameyer probably not too valuble - I can build it the html when/if I need to
15:50 pdurbin yeah, now that we have this fix you put in: https://github.com/IQSS/dataverse/pull/3516
15:50 pameyer assuming it hasn't broken again, of course ;)
15:51 * pdurbin clicks "Build Now"
15:51 pameyer * crosses fingers
15:51 pdurbin It worked back in October! :)
15:52 pdurbin still works: http://phoenix.dataverse.org/site/latest/site/apidocs/
15:53 pameyer cool
15:53 pdurbin we *could* use javadoc for https://github.com/IQSS/dataverse/issues/4549
15:53 pdurbin but I think we're leaning toward a page in the dev guide using sphinx
15:57 pameyer I think that just having it exist is good
15:58 pdurbin yeah
15:58 pdurbin or obviate the need for it :)
16:00 pameyer or that
16:11 pdurbin pameyer: you might like this: https://github.com/IQSS/dataverse/commit/b8d07d5
16:49 jri joined #dataverse
17:10 jri joined #dataverse
17:39 pameyer pdurbin: nice!
17:39 pdurbin :)
17:57 donsizemore joined #dataverse
19:09 pameyer pdurbin: any ideas how hard the students in that class are load testing dataverse?
19:10 pameyer aka - pile traffic on it until something fails, or target $x simultaneous users
19:13 pdurbin pameyer: you should watch the video: https://bluejeans.com/s/7dg33/ ;)
19:14 pdurbin In some notes I wrote "50 users ok, 69 users starts to fail"
19:14 pameyer ah - gotcha
19:14 pameyer I'll check it out later
19:15 pdurbin He got some suggestions on how to improve his load testing. Not from me. I don't have much experience with JMeter.
19:15 pdurbin It sounds like you record some actions and then play them back.
19:16 pameyer me either - I looked at it minimally, and went with ab instead
19:16 pameyer I might have even had a reason that made sense at the time...
19:18 pdurbin ab was also mentioned at https://github.com/BU-NU-CLOUD-SP18/Dataverse-Scaling#solution-concept
19:18 pdurbin I think a little load testing will be healthy for Dataverse.
19:18 pdurbin shake out some bugs
19:20 pameyer well, it's definately possible enough to load test Dataverse enough to effectively kill glassfish
19:21 pdurbin with apache bench?
19:21 pameyer if I'm remembering correctly
19:22 pameyer wasn't very powerful VM config though, which was probably a factor
19:23 donsizemore joined #dataverse
19:32 pdurbin We should probably offer more guidance on tuning and system requirements in the installation guide.
19:35 pameyer it might be helpful, but the impression I've gotten is that system load isn't a big concern for most installations
19:37 pdurbin Yeah, I'm more thinking about how much RAM we should recommend for a production installation. I'm not sure, to be honest.
20:30 donsizemore @pdurbin i would've recommended 64GB (as vmware's current upper limit for fault-tolerant VMs) but Leonid's memory improvements really helped WRT harvesting
20:43 pdurbin cool
21:03 andrewSC joined #dataverse
21:44 pameyer left #dataverse
22:05 donsizemore joined #dataverse

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.