WEBVTT

1
00:00:00.000 --> 00:00:00.840
cloud.

2
00:00:12.150 --> 00:00:14.730
Mick Coady: said, you could make or find a Co host.

3
00:00:15.690 --> 00:00:17.850
Siddhartha Ghosh: I have to make a Co host okay.

4
00:00:17.880 --> 00:00:18.540
Mick Coady: You could.

5
00:00:20.250 --> 00:00:22.560
Irfan Elahi: Or you could just share the screen whatever works.

6
00:00:23.850 --> 00:00:26.010
Siddhartha Ghosh: Let me give you.

7
00:00:27.030 --> 00:00:29.310
Siddhartha Ghosh: Make your The co host and so.

8
00:00:30.870 --> 00:00:31.170
cool.

9
00:01:02.970 --> 00:01:08.190
Siddhartha Ghosh: Okay now you are co host so you know yeah.

10
00:01:09.750 --> 00:01:11.430
Irfan Elahi: So, can you guys see my screen.

11
00:01:13.680 --> 00:01:14.820
Mick Coady: yeah are from wicked.

12
00:01:14.940 --> 00:01:15.540
Yes.

13
00:01:17.190 --> 00:01:19.230
Irfan Elahi: So let me know whenever you're ready said.

14
00:01:20.010 --> 00:01:26.400
Siddhartha Ghosh: I think you should go ahead, since we had Preston time, I would like to have as much time as possible for you.

15
00:01:27.360 --> 00:01:38.880
Irfan Elahi: yeah Thank you everyone and welcome to the kickoff for the encourage PC users group I wanted to share basically some details of the new system now, this is just.

16
00:01:39.330 --> 00:01:49.020
Irfan Elahi: The first of many engagements, we will have so i'm going to try to stay a little bit more at the high level, but we definitely plan to deep dive.

17
00:01:49.290 --> 00:01:57.390
Irfan Elahi: Especially for those user environment and the software stack and some of the internals of the hardware, including interconnect.

18
00:01:58.140 --> 00:02:04.500
Irfan Elahi: So just to give you a little bit his historical perspective we kicked off this project in June of 2018.

19
00:02:04.950 --> 00:02:15.750
Irfan Elahi: And you know I started putting the core team together almost a in June of 2018 and the core team included technical evaluation team business benchmark facility team.

20
00:02:16.110 --> 00:02:22.170
Irfan Elahi: As well as a contract and legal team, but the most important was the science requirement advisory panel.

21
00:02:22.500 --> 00:02:37.710
Irfan Elahi: Because he wanted to get input from our scientist and users are not just looking at how cheyenne was utilized and look at the metrics and data that we collected from cheyenne, but we also wanted to be forward looking so we had.

22
00:02:38.280 --> 00:02:52.230
Irfan Elahi: A number of meetings with the science requirement advisory panel and over 30 plus a use science cases that I was used to form the technical requirement for the new system.

23
00:02:52.740 --> 00:03:02.070
Irfan Elahi: We also engage the technology development divisions and other subject matter experts from within sizzle to get a very.

24
00:03:03.180 --> 00:03:13.200
Irfan Elahi: Total solution, not just from user perspective, but also from facility, as well as how we can meet in the new system going forward, because one of the most important.

25
00:03:13.530 --> 00:03:29.310
Irfan Elahi: Things that s rap and users have been pressing us on is they want more storage, but they also want system that's available and usable so we put a lot of emphasis and i'll talk a little bit more about that in detail on.

26
00:03:30.120 --> 00:03:40.110
Irfan Elahi: So the main objective of NWS he was to provide hype, a highly productive beta and intensive supercomputer for in car.

27
00:03:40.440 --> 00:03:59.040
Irfan Elahi: and users and application, but also tried to see if we can build on the success of cheyenne especially what we learn from cheyenne and also invest in s access game and gpu architecture and also cloud computing technologies, because there is a lot of.

28
00:04:01.950 --> 00:04:04.530
Irfan Elahi: Proof that these could become prevalent.

29
00:04:06.210 --> 00:04:16.680
Irfan Elahi: technologies in the next five years now also we wanted to make sure that we could enable our application to optimization and refactoring.

30
00:04:17.520 --> 00:04:36.570
Irfan Elahi: I can make use of these new technologies and also one of the guidance from pseudo Council was to make sure that the users remain productive throughout the transition to nw se and beyond, and that's why we do not plan to decommission cheyenne until the end of 2022.

31
00:04:39.660 --> 00:04:52.470
Irfan Elahi: So, after consultation and user requirements we I am looking at our budget, we decided that the new sbc systems system should be at least three times.

32
00:04:52.950 --> 00:05:05.070
Irfan Elahi: The cases same capability of cheyenne and working with the benchmark team we created a suite of bird benchmarks and that's the benchmark, you know.

33
00:05:05.400 --> 00:05:11.700
Irfan Elahi: running on all of cheyenne would get us one season or cheyenne sustained equals performance.

34
00:05:12.000 --> 00:05:23.700
Irfan Elahi: So we basically provided that sweet as well as guidance to the vendors and said, well, you must at least get minimum of three cheyenne and also we wanted 60 petabyte usable file system.

35
00:05:24.510 --> 00:05:30.840
Irfan Elahi: Another guidance and the rfp was that the split should be at 20 and the split is.

36
00:05:31.470 --> 00:05:38.580
Irfan Elahi: Not by budget or the node count, but on the cce APP itself so MC 80% of the seaside a cpu.

37
00:05:38.940 --> 00:05:50.760
Irfan Elahi: And 20% is gpu another thing that we've been kind of getting requests from not just other labs but also management and nsf is cloud bursting capability, so we did invest.

38
00:05:51.120 --> 00:06:04.770
Irfan Elahi: In cloud bursting capability in terms of deliverables it did not cost us money, but the new scheduler will have a gui interface that will allow you to launch instances on azure and aws.

39
00:06:05.460 --> 00:06:16.410
Irfan Elahi: Primary will be targeting EMS, and some of these special campaigns, because it does require additional funding, so we do not, you know so will not provide the funding.

40
00:06:17.520 --> 00:06:27.600
Irfan Elahi: If people have cloud credits are you car and car has that funded setup then users will be able to burst out the scheduler would be configured to do that.

41
00:06:28.440 --> 00:06:45.720
Irfan Elahi: And also, I won't go into too much details, but basically our plan is to start the accelerated science discovery in January 1 week of January and then maybe after three months we'll open the system to the rest of the users, we also had options to grow, the system if needed.

42
00:06:47.880 --> 00:06:53.580
Irfan Elahi: So one of the cool aspect of this pyramid which, as far as I know, we have never done in the past.

43
00:06:53.910 --> 00:07:04.710
Irfan Elahi: Is after the request for information or the Roi phase we had co design workshops, where we invited the vendor and technology providers to sit down with us for the.

44
00:07:05.190 --> 00:07:16.920
Irfan Elahi: whole day and basically kind of working side by side, you know, in a collaborative and consultative approach create solution and innovation and improvement.

45
00:07:17.430 --> 00:07:32.100
Irfan Elahi: On the rfp responses so basically the Co design outcome was we configured and architected a system that we are able to provide real time input and feedback Otherwise, what happens is that.

46
00:07:32.640 --> 00:07:48.270
Irfan Elahi: vendors respond to our rfp we look at the rfp and we don't like certain things, and then we asked them to go for an F rp and that can become problematic, but what we did here was we basically in co design workshop were able to iron out a lot of those.

47
00:07:50.400 --> 00:07:54.990
Irfan Elahi: issues and that made the rfp response more.

48
00:07:57.390 --> 00:08:09.510
Irfan Elahi: targeted towards our requirement, it was made much closer to our requirement now, we did not have a smooth sailing with this rfp there were a ton of constraints and issues.

49
00:08:10.050 --> 00:08:24.180
Irfan Elahi: One of the biggest challenges that I saw was we have limited domestic SPC vendor to a high performance computing xp acquired SGI and Korea so basically we were you know.

50
00:08:24.690 --> 00:08:34.680
Irfan Elahi: down to just IBM HP and Dell on IBM is not cost competitive they were extremely expensive, you know and the problem with.

51
00:08:35.760 --> 00:08:39.990
Irfan Elahi: Dell was that they do not provide quotes for.

52
00:08:41.250 --> 00:08:51.570
Irfan Elahi: A product that are not ready to ship, so we were asking them to quote a product that would be another 18 months away from delivery date so it was challenging for down.

53
00:08:52.200 --> 00:08:58.890
Irfan Elahi: Because our federal facility takes time, so we, you know that would be pretty much did not been.

54
00:08:59.760 --> 00:09:06.090
Irfan Elahi: The other thing is that small vendors like penguin computing and others like Aspen systems, they do not have.

55
00:09:06.450 --> 00:09:17.220
Irfan Elahi: The resources to run our benchmark because it's very resource intensive so they just sit out these kind of big pyramid and that's why i'm working with tdd and others to see if we can.

56
00:09:17.790 --> 00:09:26.100
Irfan Elahi: simplify our benchmarks, if you look at what oakridge is doing they're trying to take a lot of the workflow and put it out there on the.

57
00:09:28.530 --> 00:09:36.510
Irfan Elahi: You know, make it publicly available and make it more closer to synthetic benchmark, so we need to also look at that if you want to invite some of the smaller.

58
00:09:36.960 --> 00:09:41.160
Irfan Elahi: vendors and my apologies i'm going fast, because I don't have too much time.

59
00:09:41.760 --> 00:10:00.000
Irfan Elahi: Also code 19 added significant challenges, most of the vendors have problem getting price warranty and they also had issues with getting resources to do some of the rfp one and also there is constraint upon us that we have to buy America.

60
00:10:01.320 --> 00:10:08.670
Irfan Elahi: Because of the by America academic boo or a task and a Lenovo we're very much interested, but we could not.

61
00:10:10.260 --> 00:10:15.420
Irfan Elahi: You know, invite them because they are not American companies, so we are limited by that.

62
00:10:16.740 --> 00:10:25.260
Irfan Elahi: So what are we getting we are basically getting a cray system used to be called shasta now it's crazy ex.

63
00:10:25.830 --> 00:10:33.930
Irfan Elahi: We are the peak will be just about 20 better flop 60 petabyte usable it's about 82 petabyte of raw storage.

64
00:10:34.770 --> 00:10:48.690
Irfan Elahi: And here's The good thing the SES up that we are getting is actually 3.51 so it's more than what we had asked for and, as you can see 2.743 is on traditional cpu.

65
00:10:49.230 --> 00:11:09.600
Irfan Elahi: Which is basically an empty Milan and then the point, six, seven, you know it's almost about 70% of shine in terms of CSS is on gpu and all of these gpus are the nvidia redstone a 110 Sir or graphic processing unit.

66
00:11:11.040 --> 00:11:25.830
Irfan Elahi: gpus now, we do have confidence and create dream so we're really excited about that they have a very large install base oakridge argon nurse El capitan at Lawrence livermore and even more recently.

67
00:11:27.030 --> 00:11:33.570
Irfan Elahi: Sorry El capitan at Lawrence livermore and more recently Los Alamos also worked with the cray.

68
00:11:34.080 --> 00:11:40.710
Irfan Elahi: So that they have a pretty large install base Another thing we are doing differently with this one is that there would be an onsite.

69
00:11:41.250 --> 00:11:45.570
Irfan Elahi: person so that will reduce our time to resolution for problems.

70
00:11:45.810 --> 00:11:59.250
Irfan Elahi: And the scheduler and the system is going to be PBS so you will not have to change your job submission script, we are also planning to move all of casper from learn to PBS so going forward, we will have a single our scheduler.

71
00:11:59.850 --> 00:12:15.060
Irfan Elahi: To basically i've you know i'm not going to spend too much time on this slide this is kind of what I already discussed, I just wanted to share that graphics of what the racks will look like and I will share the slides with the set so he can put it out there.

72
00:12:16.890 --> 00:12:33.720
Irfan Elahi: Some more details, so there are about 2570 nodes total are 2488 our compute while at to our gpu the cpu nodes will have our dual socket 64 core 2.6 gigahertz Milan.

73
00:12:34.110 --> 00:12:43.740
Irfan Elahi: Our cpu these are seven X one too, but I appreciate, if you don't share that out because amd has asked us not to these are not yet publicly.

74
00:12:46.020 --> 00:12:52.200
Irfan Elahi: available, so this is under nda please don't share some of these details on gpu, as I mentioned, is.

75
00:12:52.770 --> 00:13:03.120
Irfan Elahi: You know we'll have a single socket SMB 64 for same host cpu as the as the other one, but it also has four nvidia redstone.

76
00:13:04.080 --> 00:13:18.360
Irfan Elahi: gpus, these are all SMS for which means this all will be envy link interconnected for gpu direct and also all of these will have 40 giga Bytes of high bandwidth memory, these are all hdmi to.

77
00:13:20.280 --> 00:13:28.110
Irfan Elahi: memory, the interconnect on this is the crease slingshot it's about 200 gigabit per second.

78
00:13:29.400 --> 00:13:38.580
Irfan Elahi: per direction and the latency is a you know 1.7 2.6 microseconds so it's pretty comparable to my Linux.

79
00:13:39.360 --> 00:13:52.290
Irfan Elahi: Now, it will also have a login nodes six login nodes are just pure cpus like two of them are more you know have cpus but also have gpu is more for compile ation and on interactive work.

80
00:13:54.930 --> 00:14:05.400
Irfan Elahi: The operating system on the new system is a variant or a micro community of susie Linux it's crazy Linux environment, as I mentioned that the schedule will be PBS.

81
00:14:05.670 --> 00:14:16.980
Irfan Elahi: But we do plan to support all kind of container especially any container that has supports the open container initiative standard will be supported on this machine, especially docker and singularity.

82
00:14:17.790 --> 00:14:27.660
Irfan Elahi: For programming environment, you have the CV or the programming environment that will support open MP 4.5 as well as mpi version 3.1.

83
00:14:27.870 --> 00:14:35.880
Irfan Elahi: The create performance analysis tool will be included, and then we also have the nvidia compiler environment, just to make you aware of the.

84
00:14:36.480 --> 00:14:42.840
Irfan Elahi: nvidia compiler environment that formerly this was called PGI now it's more of freely downloadable.

85
00:14:43.320 --> 00:14:51.840
Irfan Elahi: compiler, but we will have full support on this which the free version does not so we do have the PCs, I think, is what nvidia calls it.

86
00:14:52.320 --> 00:15:05.280
Irfan Elahi: So we will be able to escalate our problems, and then we'll have 50 seats of Intel Palo studio as well, and then the file system, as you will notice is different, its luster and not GPS.

87
00:15:05.880 --> 00:15:21.000
Irfan Elahi: Now I will encourage you to discuss with Sid and others and i'll also be attending these ad hoc meetings, if you have requirement for other software stack but also reach out to Brian Wendy Wendy who's the lead from the application side for NWS see.

88
00:15:21.540 --> 00:15:41.970
Irfan Elahi: For storage I mentioned 60 petabyte usable if you can expand it or develop if we have the money in the future, it has about 300 giga Bytes per second aggregate bandwidth, but we will also connected to glade and our campaign storage and from there, it will have 200 gigabyte you know.

89
00:15:43.620 --> 00:15:52.590
Irfan Elahi: We plan to use a flash for a Meta data and, as I mentioned before, it will have luster file system and not GPS.

90
00:15:54.030 --> 00:15:57.090
Irfan Elahi: So I just wanted to give you a little bit quick background.

91
00:15:58.710 --> 00:16:04.020
Irfan Elahi: On the on the different type of nodes so the correct cabinet which they call a lump us.

92
00:16:04.380 --> 00:16:14.190
Irfan Elahi: basically consists of eight chassis and each of these chassis can support it compute blades which are in the front and eight network leads, which are installed in the rear of the cabinet.

93
00:16:14.550 --> 00:16:21.150
Irfan Elahi: Now the good thing about these kindnesses there is no black plane in the chassis to provide network connection between the compute blades.

94
00:16:21.510 --> 00:16:29.670
Irfan Elahi: it's actually auto no connections between the network blades and the compute blades that act provide the network connections, so this is different than cheyenne.

95
00:16:29.910 --> 00:16:40.020
Irfan Elahi: And the benefit of this that without having a bad plan it means nothing is hardwired so we can simply swap out the nodes are you know to.

96
00:16:40.710 --> 00:16:49.770
Irfan Elahi: Change the network blades and so you know you're not tied to to you know, a one type of cpu and lot of.

97
00:16:50.580 --> 00:17:02.790
Irfan Elahi: vendors what they're doing is they say that these cabinets can have a life of 10 years, so instead of completely taking everything off the floor and replacing it, you can simply replace the computer late again that's something to see.

98
00:17:03.300 --> 00:17:09.090
Irfan Elahi: Now, each of these are cabinets cab home 64 compute blades and 64 switch plates.

99
00:17:09.990 --> 00:17:16.290
Irfan Elahi: And, and you can have 256 cpu only nodes are 128 gpu only known.

100
00:17:16.620 --> 00:17:29.340
Irfan Elahi: The cpu nodes are you know will have eight memory channels that are fully populated with one dimple channel all of these are dual rank memory, especially because we want to provide the optimal memory performance.

101
00:17:29.640 --> 00:17:35.760
Irfan Elahi: And we are giving you guys a sufficient that ability of 256 gigabyte of memory.

102
00:17:36.480 --> 00:17:48.900
Irfan Elahi: per node for the cpu for the gpu nodes it will have 512 instead of 256 again all memory child are fully populated with DDR for 3200 Dems.

103
00:17:49.680 --> 00:18:09.210
Irfan Elahi: You know, an e gpu is configured, as I mentioned before, single socket for nvidia gpus are not the difference between a cpu and gpu node in terms of net network is that gpu nodes would have for network injections get to that will give you almost 800 gigabits per second.

104
00:18:11.610 --> 00:18:24.120
Irfan Elahi: So just to touch on luster the power five file system will not be dp fs it will be luster and it's going to use cluster store he 1000 our hardware, which is.

105
00:18:24.720 --> 00:18:37.200
Irfan Elahi: crazy and it will be concerning do into a single luster file system called scratch and it will have a single namespace that is posits compliant and you can access it through a single mount point we.

106
00:18:37.980 --> 00:18:48.990
Irfan Elahi: expect that the file system scrubbing policy will be about six months or even more so, you will see a different scratch scrubbing policy, not the 90 day you have right now.

107
00:18:50.940 --> 00:19:00.930
Irfan Elahi: So very quickly touching on something that is you know rasen basically reliability availability serviceability usability and manually and.

108
00:19:02.190 --> 00:19:09.210
Irfan Elahi: said, this is not the the south Indian Curry rossum that you and I are aware of this is a different.

109
00:19:09.570 --> 00:19:20.460
Irfan Elahi: So basically what we are trying to do is make sure that electrical and mechanical components are ups, we want to make sure that the story and file system has a higher availability, which is 99%.

110
00:19:20.730 --> 00:19:27.390
Irfan Elahi: But we are also trying to take advantage of features and functions that Christmas and provides for higher rassam.

111
00:19:28.200 --> 00:19:34.680
Irfan Elahi: You know, and this is something we've been very, very focused on while working to architect, the system with the cray.

112
00:19:35.640 --> 00:19:49.110
Irfan Elahi: This is an interesting slide that you might want to look at in your free time but it gives you the history of supercomputing at n car from 1960s to 2025 because that's when you know we plan to keep operating the new system.

113
00:19:50.130 --> 00:20:01.620
Irfan Elahi: it's I know it's pretty small, but you can magnify it and I, this is mostly in your free time you can look at it, so this is a good slide that I wanted to share with you, it gives you a little bit.

114
00:20:02.760 --> 00:20:14.190
Irfan Elahi: idea of how much flops the new system will be so you will see with cheyenne and the new system, we will be above 25 pepper flops.

115
00:20:15.060 --> 00:20:22.080
Irfan Elahi: And then, this is similar but it gives you the storage capacity, if you look at campaigns to read with the 66 petabyte.

116
00:20:22.350 --> 00:20:36.570
Irfan Elahi: glade which is 38 by by object store, which is five and then you look at the 60 petabyte that will come, so we have a lot of storage once the system will get installed, obviously we will start decommissioning some of the older.

117
00:20:37.890 --> 00:20:49.080
Irfan Elahi: storage in blade this kind of just gives you the maximum power consumption so you'll see will be reaching close to 4.5 megawatt megawatts a year.

118
00:20:49.860 --> 00:21:00.450
Irfan Elahi: You know, if I may be mistaken, but I think cheyenne city is four or five megawatt total but anyway that's just off the top of my head don't hold me to it.

119
00:21:01.290 --> 00:21:21.960
Irfan Elahi: This is a slide that I really like because it gives you the sustained mega flop per second per Watt if you compare cheyenne which has about 73 sustain mega flop or walk while the new system will have hundred and 71 So you can see that the new system is much more energy efficient.

120
00:21:24.720 --> 00:21:34.260
Irfan Elahi: This is my final slide I couldn't go, not the final there's one more, but this kind of gives you when we will be accepting this machine, I hope, to complete the acceptance test in December.

121
00:21:34.620 --> 00:21:42.660
Irfan Elahi: Open it for an accelerated science discovery in January and then in late March early April, it will be open to all the users.

122
00:21:44.580 --> 00:21:56.250
Irfan Elahi: I also wanted to touch on some things we are doing on casper you will be also hearing about this at the Web talk tomorrow, but we are adding we added recently a new gpu nodes.

123
00:21:56.670 --> 00:22:07.140
Irfan Elahi: we've also moved RD off of to their own dedicated node lot of users were complaining about that that idea was kind of had longer Q where wall clocks so they were kind of.

124
00:22:08.310 --> 00:22:18.030
Irfan Elahi: causing issues, but we also adding 64 high throughput computing knowledge, these will all have SDR you know trainer at four gigabyte memory.

125
00:22:18.600 --> 00:22:30.180
Irfan Elahi: They will be new dedicated login nodes on casper this was another user requirement and then, as I mentioned, learn will be migrated to PBS so you will have a common scheduler across the board.

126
00:22:30.690 --> 00:22:38.730
Irfan Elahi: So that kind of ends my slides i'm four minutes overtime any questions, I will be happy to take that.

127
00:22:42.690 --> 00:22:51.120
Brian Vanderwende: So are found there were a couple questions that popped up into the chat one from Jim edwards is will gpu direct storage be available.

128
00:22:54.660 --> 00:22:57.270
Irfan Elahi: So that's something we have not.

129
00:22:58.830 --> 00:23:06.930
Irfan Elahi: looked at, but I would like to get some our requirement from Jim you know what does.

130
00:23:08.100 --> 00:23:16.290
Irfan Elahi: He mean by gpu direct storage and and and how will he take advantage of it and absolutely we can look into it.

131
00:23:18.480 --> 00:23:32.100
Irfan Elahi: So I need that you know so sit, maybe, can you work with the and Brian both of you are, because these are two different you know and get has a requirement and then definitely I think that's a very interesting question.

132
00:23:33.240 --> 00:23:35.130
Brian Vanderwende: yeah we'll follow up with Jim that sounds good.

133
00:23:36.030 --> 00:23:43.260
Mick Coady: Another question or fun from ethan gutman was how will cloud bursts interact with glade or other storage.

134
00:23:44.130 --> 00:23:50.280
Irfan Elahi: So that's actually pretty challenging because one of the challenges of cloud is that you know.

135
00:23:50.730 --> 00:24:01.380
Irfan Elahi: You can't run in the cloud, you can firing and then just run something unless you have the data, you need to run your jobs, so you know, there are very.

136
00:24:02.010 --> 00:24:12.630
Irfan Elahi: Few different options, you know one is that you basically have some kind of a data common data Center environment that's very readily accessible it's on the edge of cloud.

137
00:24:13.740 --> 00:24:22.560
Irfan Elahi: You know, and there are ways to do that, the other is that you basically get some persistent storage on the cloud where you can pre staged your data before you run it.

138
00:24:22.800 --> 00:24:32.250
Irfan Elahi: that's really costly, because you have to continuously pay for that persistent cloud the other option that we can do is you basically upload your data.

139
00:24:32.700 --> 00:24:44.640
Irfan Elahi: Fire you know after you have your instance ready run your job when you're done you download your data back, but then that has its own challenges, because you have to pay for moving data to and from the cloud.

140
00:24:45.420 --> 00:24:51.420
Irfan Elahi: You know so right now, all of these things are being looked at, I think.

141
00:24:51.960 --> 00:24:59.970
Irfan Elahi: You know, over the next few months and couple of years, we need to find a happy medium that works for us and is cost effective.

142
00:25:00.360 --> 00:25:16.500
Irfan Elahi: But as I said, you know, there are costs involved in all of these my my apologies, I have to jump into another abr meeting I will be more than happy to come back at the next meeting and answer additional questions.

143
00:25:20.190 --> 00:25:22.290
Irfan Elahi: said is that Okay, if I drop off.

144
00:25:23.220 --> 00:25:27.720
Mick Coady: Okay, I think we can hit, I think we can handle it from your phone Thank you.

145
00:25:27.780 --> 00:25:28.440
Irfan Elahi: very much.

146
00:25:28.890 --> 00:25:29.580
Siddhartha Ghosh: Thank you, it fun.

147
00:25:30.660 --> 00:25:44.010
Mick Coady: So one of the questions to the group was Dave Gill asked a good question about the nda parts that are fine alluded to, I believe he was referring to the clock speeds on the chips.

148
00:25:46.050 --> 00:25:47.100
Mick Coady: At that point Dave.

149
00:25:57.630 --> 00:26:01.290
Siddhartha Ghosh: Any more questions make or Brian that we should be discussing.

150
00:26:01.530 --> 00:26:03.210
Brian Vanderwende: Yes, good.

151
00:26:03.720 --> 00:26:05.550
Mick Coady: Go ahead, Brian go ahead, sorry.

152
00:26:07.140 --> 00:26:11.700
Brian Vanderwende: yeah so john Klein asked about the luster file system and if it's going to be mounted on casper.

153
00:26:13.200 --> 00:26:30.750
Brian Vanderwende: And I see bill Anderson is in this meeting, so he could speak to this as well, but I believe that the the luster is, it should be mounted on to casper as far as the GPS storage being mounted on wc three I think the current plan is is no.

154
00:26:32.550 --> 00:26:38.670
Brian Vanderwende: But, and specifically i'm talking about the the the the scratch space.

155
00:26:39.720 --> 00:26:45.270
Brian Vanderwende: In glade but again bill can speak more to that if he if he has anything to add.

156
00:26:47.460 --> 00:26:51.450
Bill Anderson: hi Brian yeah some of those plans are still being finalized.

157
00:26:52.500 --> 00:27:04.170
Bill Anderson: Like you said, and I know Jared on this call, he could weigh in as well, but our plan is to mount the scratch from NWS see three onto casper there is discussion about mounting.

158
00:27:05.460 --> 00:27:17.280
Bill Anderson: Some of the campaign's tour and home file system current home file system on to end with three but but no final decision has been made there is my understanding.

159
00:27:19.050 --> 00:27:19.560
Brian Vanderwende: Thanks so.

160
00:27:24.660 --> 00:27:32.640
Mick Coady: I think said I think that's it for questions, so I apologize if I missed, one that someone asked earlier.

161
00:27:34.680 --> 00:27:42.390
Siddhartha Ghosh: Okay yeah that's suddenly we can go back to the questions and all my, as I mentioned in the beginning, the.

162
00:27:43.020 --> 00:28:03.120
Siddhartha Ghosh: Whole session is being recorded any of the issues that we haven't addressed, we can come back to the next meeting, and this will be a monthly meeting, as we have mentioned earlier in our weekly, so let me get on to the this user group structure, what we are expecting so.

163
00:28:04.320 --> 00:28:06.000
Siddhartha Ghosh: Can you see my slide.

164
00:28:08.460 --> 00:28:09.030
rgarcia: Yes.

165
00:28:09.510 --> 00:28:29.670
Siddhartha Ghosh: Okay, so here here is what we had as agenda, we already covered it founds top and then few logistics, I will get to that in a minute I will to group, and this meeting series, the structure of the meetings and communications that we would like to have.

166
00:28:30.690 --> 00:28:41.760
Siddhartha Ghosh: Our current priorities and then, finally, I will hand over to Brian for application team perspective, once we get to that we will know more about it.

167
00:28:42.900 --> 00:28:57.180
Siddhartha Ghosh: So a few logistics all meetings in the series will be recorded well, the only reason we want to do that is to be able to capture all the conversations that will be happening, and as you realize that a lot of people in the meeting.

168
00:28:57.600 --> 00:29:08.730
Siddhartha Ghosh: And we need to capture most of the opinions or most of the questions that you have or concerns you have so that we, we are able to address those.

169
00:29:09.600 --> 00:29:20.730
Siddhartha Ghosh: We will share with Members the recordings minutes agenda slides etc all participants muted, by default, as you join as you probably have noticed already.

170
00:29:21.870 --> 00:29:26.100
Siddhartha Ghosh: Comments question us raise hand feature, if you want the.

171
00:29:26.190 --> 00:29:27.960
Mick Coady: We want to speak.

172
00:29:28.410 --> 00:29:47.100
Siddhartha Ghosh: or just flashing the chat window, as you have been doing already or we are monitoring the chat you may email this a mailing list anytime for the low end of this response, which will be a little more persistent response over there it's a shared inbox type.

173
00:29:48.870 --> 00:29:52.020
Siddhartha Ghosh: group, where we, we will be monitoring all the males.

174
00:29:53.970 --> 00:30:08.130
Siddhartha Ghosh: Then about in hug and the meetings, this is a user group user group that is for you and by you, your needs, this is about your needs how you want us to serve you.

175
00:30:08.970 --> 00:30:21.180
Siddhartha Ghosh: about our services, what do you like do not like we do not have guarantee, but you want us to offer you have experienced elsewhere, you want us to offer, for example.

176
00:30:22.140 --> 00:30:33.390
Siddhartha Ghosh: Already in the chat window, you will you have seen the mention about the docker container came, so we do not have a very extensive very know what to call.

177
00:30:35.010 --> 00:30:43.470
Siddhartha Ghosh: elaborate or more extended support for docker container currently, but we do support docker container but similarly.

178
00:30:44.880 --> 00:30:58.140
Siddhartha Ghosh: that's just an example, many other things that we do not support currently, but if you need us or want us to offer this is the forum, we would like you to Boise are concerned.

179
00:31:00.240 --> 00:31:15.180
Siddhartha Ghosh: about the meeting, ideally, we administer and set platform for your voice, so it is your platform, or we are just giving you the context, so that you were able to speak.

180
00:31:15.900 --> 00:31:35.880
Siddhartha Ghosh: Up you want to organize it differently it's up to you, we are just giving you this organization to modify to your needs now the Community communication well the easiest way to communicate will be send a mail to get you caught it to sorry.

181
00:31:37.170 --> 00:31:38.100
Siddhartha Ghosh: Give me a second.

182
00:31:52.020 --> 00:31:52.860
Siddhartha Ghosh: sorry about that.

183
00:31:56.070 --> 00:31:56.490
Siddhartha Ghosh: So.

184
00:31:57.780 --> 00:31:58.830
What is happening.

185
00:32:04.350 --> 00:32:08.100
Brian Vanderwende: So I think if you use, you know arrow keys to move on the slides.

186
00:32:08.130 --> 00:32:10.980
Siddhartha Ghosh: Instead of clicking probably that's better.

187
00:32:11.130 --> 00:32:12.000
sorry about that.

188
00:32:18.600 --> 00:32:18.840
yeah.

189
00:32:20.100 --> 00:32:28.560
Siddhartha Ghosh: So this is our web page, we in the invitation mail I have given the link of this page.

190
00:32:29.760 --> 00:32:47.850
Siddhartha Ghosh: This the wiki the wiki is our primary communication medium where you, we can have persistent storage of all of our communication in all the sharing that we will need to have will be there all the meeting minutes recordings, etc.

191
00:32:49.530 --> 00:32:51.330
Siddhartha Ghosh: Anything you want to.

192
00:32:52.410 --> 00:33:00.810
Siddhartha Ghosh: create a new page or add a comment add an agenda for future, a future meeting, this is the place where you would.

193
00:33:02.160 --> 00:33:03.240
Siddhartha Ghosh: Go and.

194
00:33:04.650 --> 00:33:11.460
Siddhartha Ghosh: replace your concern, so they are women teenager minutes slides links to recordings, etc.

195
00:33:13.320 --> 00:33:31.050
Siddhartha Ghosh: Current priorities in wc three obviously then next year by this time we'll have the machine fully in production so, particularly to give the gpu partitions enterprise, as you all know, our flagship codes.

196
00:33:32.220 --> 00:33:43.680
Siddhartha Ghosh: not suited for gpu partitions so we want new applications either email deal or any model like empathic or any other models.

197
00:33:45.000 --> 00:33:47.760
Siddhartha Ghosh: That are that have been already voted on to gpu.

198
00:33:49.470 --> 00:34:03.720
Siddhartha Ghosh: To focus on gpu partitions is the port projects for gpu participants your training needs anything that we are missing, this is just to give you an example of things that we need to discuss over here.

199
00:34:05.220 --> 00:34:17.820
Siddhartha Ghosh: And then I hand over to Brian Brian for more detail about the application day focus or in wc three brand new tech from here.

200
00:34:18.420 --> 00:34:27.990
Brian Vanderwende: yeah thanks said so i'll just briefly describe what what our team is doing right now so there's there's a bunch of deployment teams that have been structured.

201
00:34:28.980 --> 00:34:46.590
Brian Vanderwende: As we you know, work towards the deployment of NWS C three and one of the teams that Ray Kelly, and I are leading is this application team, I would say, this is the most user centric team were concerned about things like application readiness, we want to make sure that.

202
00:34:47.790 --> 00:34:58.980
Brian Vanderwende: Our you know our flagship codes, but also these newer codes are ready to run on NBC NBC three and, similarly, the end of usc three is ready to run those codes.

203
00:35:00.330 --> 00:35:11.070
Brian Vanderwende: We want to make sure that anybody who's interested in getting spun up using gpus or it has questions about say the PBS scheduler configuration or.

204
00:35:14.220 --> 00:35:20.970
Brian Vanderwende: Concerns about the amd chips or anything like that that we can make sure that you feel like you're ready to move to the new machine when it's deployed.

205
00:35:21.690 --> 00:35:37.830
Brian Vanderwende: we're also charged with constructing or at least prototyping the user environment so things like you know the software stack things that work well for you right now things that you anticipate being a challenge, maybe in a more heterogeneous computing environment.

206
00:35:38.970 --> 00:35:47.880
Brian Vanderwende: Those are the kinds of things that we're interested to do some outreach and get your feedback on so you know that doesn't have to happen in this meeting, of course, because.

207
00:35:48.480 --> 00:35:54.600
Brian Vanderwende: These are, these are parallel efforts, I would say, but I just want to bring attention to what we're doing and.

208
00:35:55.020 --> 00:36:12.240
Brian Vanderwende: If you want to reach out to us about any of these concerns, you can send myself and or rory an email and we'll certainly be in touch and things like you know some of the questions that have come up here about you know how workflow managers will work with the.

209
00:36:13.770 --> 00:36:27.750
Brian Vanderwende: With the PBS configuration for the scheduler and you know it certainly any questions about gpu computing and how we intend to structure that on the new machine, those are great things for us to discuss with you, moving forward.

210
00:36:28.770 --> 00:36:33.420
Brian Vanderwende: So yeah that's a that's kind of just a summary of what will be will be doing.

211
00:36:38.250 --> 00:36:44.130
Siddhartha Ghosh: Okay, so well, we are now opening the floor, you can ask questions over the chat or.

212
00:36:46.650 --> 00:36:54.600
Siddhartha Ghosh: Even mean you know if you want us prefer to speak just let us know abroad or you can unmute yourself If not, our will and will.

213
00:36:55.830 --> 00:36:55.980
Brian Vanderwende: fix.

214
00:36:56.490 --> 00:37:00.180
Ethan Gutmann: I just I just asked this in the chat but i'll repeat it here i've.

215
00:37:00.420 --> 00:37:12.510
Ethan Gutmann: i've had issues getting code to compile and create a system it's just because they they wrapped different compilers and all sorts of weird ways can we get access to some kind of small test system with the cray programming environment built on it.

216
00:37:12.990 --> 00:37:15.600
Ethan Gutmann: So that we can test out our compilation at a time.

217
00:37:16.920 --> 00:37:19.350
Brian Vanderwende: yeah so so i'll speak to that.

218
00:37:20.790 --> 00:37:33.780
Brian Vanderwende: We have, I guess, a number of different stages of access that we're looking into in the short term we're hoping we're trying to get access and we're planning to get access to some HP internal machines to play with that.

219
00:37:34.770 --> 00:37:45.720
Brian Vanderwende: You know that that'll probably be just you know our applications team and some other select folks, but we will have a test machine that gets deployed late in the summer.

220
00:37:46.650 --> 00:37:53.730
Brian Vanderwende: That you know will be our machine and I think at that point we can we can work more closely with folks.

221
00:37:54.270 --> 00:38:12.330
Brian Vanderwende: In terms of getting all the wrinkles out of that that great computing alarm, because that that is one of the risks that we're paying attention to is is making sure that you know our default compiler and mpi and software stack that we get from the vendor plays nicely with our applications.

222
00:38:13.920 --> 00:38:14.280
Thanks.

223
00:38:20.820 --> 00:38:25.650
Siddhartha Ghosh: More questions, and particularly the university folks I know inertia wyoming folks.

224
00:38:27.240 --> 00:38:28.770
Siddhartha Ghosh: were pretty quiet so.

225
00:38:37.530 --> 00:38:40.770
Kartik Iyer: Hello hi yeah it's got the here.

226
00:38:42.090 --> 00:38:44.820
Kartik Iyer: For the new machine will be testing a few.

227
00:38:47.790 --> 00:38:51.840
Kartik Iyer: Standard codes to check the performance of the machine and.

228
00:38:53.580 --> 00:38:57.450
Kartik Iyer: What will be the process of selecting those codes from your end.

229
00:39:02.370 --> 00:39:08.220
Siddhartha Ghosh: Okay, let me take that first and you take it from there guarding.

230
00:39:09.240 --> 00:39:09.720
Siddhartha Ghosh: The.

231
00:39:10.890 --> 00:39:24.600
Siddhartha Ghosh: As I mentioned, our process of selection of this machine is based on the performance or the capacity, so we already have a nw sc benchmark suite.

232
00:39:25.470 --> 00:39:38.520
Siddhartha Ghosh: For that and different applications has different weight associated with the performance contribution and that's how we get to that factor of, say, 3.5.

233
00:39:39.600 --> 00:39:53.100
Siddhartha Ghosh: cheyenne equivalent and things like that So yes, vendors are required by the contract to make the cheyenne equivalent performance that they have.

234
00:39:53.520 --> 00:40:11.910
Siddhartha Ghosh: projected to get out of this machine if they fall short of that they will have to provide additional hardware or thing mo a bit bs back in terms of money or this needs to be discussed how they will compensate that but there by contractually they are required to.

235
00:40:13.260 --> 00:40:18.810
Siddhartha Ghosh: Keep the performance level that they have committed to for the money that we are paying to them.

236
00:40:19.350 --> 00:40:34.620
Kartik Iyer: gotta tanks ashutosh out one more follow up question so once the machine is up and running, then you have like an early user user period where we can test our code, so that when you're applying for computer time we can use that say scaling data.

237
00:40:35.790 --> 00:40:46.680
Siddhartha Ghosh: Yes, you will have to do that in fact the earphone spoke about he is the period advanced scientific discovery roughly we are expecting.

238
00:40:47.250 --> 00:41:08.070
Siddhartha Ghosh: If everything goes well from January to January 1 2022 till April 1 2022, we will have this three month period dedicated to advanced scientific discovery and this will be a mega project to something like 20 million or more hours.

239
00:41:09.300 --> 00:41:26.520
Siddhartha Ghosh: No pride scientific project that needs to be completed within this to be three month period now in order to apply for this project, the first thing you need, we need to ensure that the codes are ready to run scale well and.

240
00:41:28.110 --> 00:41:39.900
Siddhartha Ghosh: But farms well into the machine so obviously there will be our early user Phase I you'd assume it will the prior to January MINS maybe December sometime.

241
00:41:40.530 --> 00:41:55.020
Siddhartha Ghosh: When you need support your code and it needs to come up with the performance number in order to show that your code is performing when now is the process will start in my.

242
00:41:56.520 --> 00:41:59.130
Siddhartha Ghosh: Microsoft wall says right, it will be something like.

243
00:42:00.330 --> 00:42:02.520
Siddhartha Ghosh: September timeframe this year.

244
00:42:03.690 --> 00:42:12.540
Siddhartha Ghosh: So you may have to produce the benchmark numbers from some other platform like cheyenne if you are not planning to use the gpu partition.

245
00:42:14.730 --> 00:42:24.750
Siddhartha Ghosh: To come up with a projection that how you your code will perform on new in wc three grey system but.

246
00:42:25.800 --> 00:42:34.020
Siddhartha Ghosh: After the system is come back up online, certainly, you have to read tweak your code to get to what where you have projected to.

247
00:42:35.070 --> 00:42:36.750
Kartik Iyer: Okay, thanks, a lot so.

248
00:42:37.440 --> 00:42:44.160
Mick Coady: I said said, been asked a good question to related to asd about when.

249
00:42:45.570 --> 00:42:49.440
Mick Coady: When do we expect that the calls for asd projects will be going out.

250
00:42:51.990 --> 00:42:58.650
Siddhartha Ghosh: A little bit floyd but my crystal ball says it will be some time during August September timeframe.

251
00:43:00.150 --> 00:43:16.830
Siddhartha Ghosh: And Ben is one of the priority is the participants I believe so, certainly will will contact him directly and otherwise there will be nsf solicitation for this as the project is the is much bigger than the usual enter allocation process.

252
00:43:18.210 --> 00:43:22.110
Siddhartha Ghosh: On much wider segments that we usually say this.

253
00:43:23.310 --> 00:43:24.150
Siddhartha Ghosh: In a wider.

254
00:43:25.650 --> 00:43:27.750
Siddhartha Ghosh: You user base our circulation.

255
00:43:29.970 --> 00:43:43.560
Mick Coady: Then let's note that answers your question or not so and then Dave Gill had another good question about internal training, you know for user training on gpus and would that.

256
00:43:45.480 --> 00:43:50.100
Mick Coady: fit under the applications effort that brian's been talking about, I believe.

257
00:43:52.230 --> 00:43:58.680
Mick Coady: It it won't directly fall under the gave and will fall under directly under the applications teams.

258
00:44:00.450 --> 00:44:11.520
Mick Coady: charter or effort, but we have a parallel effort going on within sizzle that we've aranka has tagged the gpu tiger team.

259
00:44:12.570 --> 00:44:18.360
Mick Coady: Most of consulting group is involved in that, as well as some of the other there's some Members.

260
00:44:19.740 --> 00:44:40.290
Mick Coady: Of you folks who are in this meeting, who are also going to be part of that and the training for users, both internal to sizzle internal to end car and and universities will be the responsibility of that gpu tiger team and you'll be hearing more about that here very shortly.

261
00:44:48.330 --> 00:44:52.110
Brian Vanderwende: So said there's a question from JEREMY sour and I think.

262
00:44:53.490 --> 00:45:02.520
Brian Vanderwende: You know, you can take this one so it's is there any notion of how allocations and charging will work for gpus will gpu nodes be a separate Q from cpu nodes.

263
00:45:04.350 --> 00:45:11.130
Siddhartha Ghosh: JEREMY This is something we are discussing at this point in time, of the framework, what we are.

264
00:45:12.300 --> 00:45:18.600
Siddhartha Ghosh: leaning more I would say is GP will be completely separate out of the.

265
00:45:19.620 --> 00:45:27.060
Siddhartha Ghosh: usual allocation poll that this system will have our any of our system has currently.

266
00:45:28.740 --> 00:45:29.220
Siddhartha Ghosh: So.

267
00:45:31.080 --> 00:45:33.480
Siddhartha Ghosh: It will be on the project basis.

268
00:45:33.480 --> 00:45:36.390
Siddhartha Ghosh: When either form university or from.

269
00:45:36.420 --> 00:45:38.070
Siddhartha Ghosh: An car or elsewhere.

270
00:45:39.330 --> 00:45:41.850
Siddhartha Ghosh: Users may request for gpu resources.

271
00:45:43.080 --> 00:45:48.000
Siddhartha Ghosh: For dedicated run and though the file system and other things will be shared.

272
00:45:49.350 --> 00:46:03.570
Siddhartha Ghosh: The gpu partition and they will be completely separate and there will be separate you for gpus now we'll be here i'm assuming the application is such that.

273
00:46:05.010 --> 00:46:26.460
Siddhartha Ghosh: If it is gpus and take application, it will be running on gpu and cpu centric will be on cpu but could there be applications were part of it is really running on gpu partition and communicating with its other part which is mainly cpu partition in theory, this is possible.

274
00:46:27.780 --> 00:46:28.290
Siddhartha Ghosh: In.

275
00:46:29.880 --> 00:46:45.660
Siddhartha Ghosh: Even in practice the system will support such applications, but in practice will such applications show up in our mix I doubt very much but, if indeed it is or will be flexible to that as well.

276
00:46:47.610 --> 00:46:50.880
Supreeth Suresh: i'm sorry I said just to follow up on that.

277
00:46:51.960 --> 00:47:08.520
Supreeth Suresh: The thing you said just now, if we have a mix so currently it's not doable on casper and Chan, but it will be doable on end wc three, where we have a mix of cpu doing one task and mix of gpu doing under the desk yeah yeah that's right.

278
00:47:09.240 --> 00:47:26.970
Siddhartha Ghosh: that's exactly that is single mpi applications can have a gpu portions running on the gpu partition and the cpu portions are running on the sequel partitions and communicate with each other, under the same or y combinator yes, thank you.

279
00:47:27.300 --> 00:47:34.050
Supreeth Suresh: yeah I was thinking of, for example, CSM if we replace some dynamical core with the gpu model we can.

280
00:47:35.070 --> 00:47:43.890
Supreeth Suresh: run CSM like that get the dynamical code will be running on gpu and other dynamical call for example ocean model.

281
00:47:45.690 --> 00:47:48.120
Siddhartha Ghosh: Yes, this is very much possible yes.

282
00:47:51.000 --> 00:48:03.540
Mick Coady: Okay, said jms to another good question to says, can you talk more about how glade in the new file system will interact and what will happen to Grade one showing in his decommissioned.

283
00:48:05.790 --> 00:48:06.090
Siddhartha Ghosh: Okay.

284
00:48:06.990 --> 00:48:19.110
Siddhartha Ghosh: glick is the current glade I mean not that campaign storage campaign storage is also under the same glade partition some so.

285
00:48:20.340 --> 00:48:26.460
Siddhartha Ghosh: Current glade will go every the project and the collection space will go every with the cheyenne.

286
00:48:27.600 --> 00:48:31.050
Siddhartha Ghosh: step is that quite right bill.

287
00:48:32.940 --> 00:48:50.460
Bill Anderson: yeah so yeah the blade scratch that's on cheyenne that would go away when cheyenne goes away that's my understanding of course there's the new there'll be new scratch on and wc three things like work and P that are currently in glade.

288
00:48:51.480 --> 00:49:07.890
Bill Anderson: that'll be those will be transitioned over into campaign storage space is the current guidance we're getting from management, in other words kind of long, so it will need to last longer beyond and not be purged would be part of kind of campaign store in some fashion.

289
00:49:09.930 --> 00:49:18.750
Bill Anderson: And file system on NWS see three the native file system there will just be scratch i'm not sure that addressed the question Jim or not.

290
00:49:23.640 --> 00:49:29.430
Mick Coady: yeah bill I think it's probably safe to say that nothing is set in stone, yet right that's.

291
00:49:29.520 --> 00:49:39.330
Mick Coady: Right little lot of these policies and and decisions are still being worked out and, in fact, what were some of the guidance we're looking for from this group.

292
00:49:40.410 --> 00:49:40.890
Mick Coady: To help.

293
00:49:42.480 --> 00:49:45.000
Mick Coady: form those policies, yes.

294
00:49:45.300 --> 00:49:54.870
Siddhartha Ghosh: yeah So if you have any opinions along this line, we very much want to to wise that or any users here.

295
00:49:56.130 --> 00:50:00.780
Siddhartha Ghosh: I invite you to revise your preference and things like that.

296
00:50:01.800 --> 00:50:06.420
Mick Coady: said, perhaps, since this is so, you know, obviously a very important.

297
00:50:07.770 --> 00:50:21.840
Mick Coady: message matter to us to all users, might we might consider if it's if the rest of the group is okay with it is making that an agenda item or a discussion item that next month's meeting.

298
00:50:23.250 --> 00:50:26.910
Mick Coady: Or at the storage advisors meeting which a lot of these folks are part of.

299
00:50:30.390 --> 00:50:39.270
Brian Vanderwende: yeah just that I mean you know to level set on that you know, obviously, about the hardware has been procured you know we have this.

300
00:50:39.930 --> 00:50:51.210
Brian Vanderwende: 60 petabytes of last year, coming in and and you know there's other moving parts with storage hardware, but a lot of the way that it's structured and the policies and the quotas.

301
00:50:52.380 --> 00:51:00.030
Brian Vanderwende: How it's partitioned you know that there's certainly still flexibility on that, so this is, you know the earlier, we can get that input.

302
00:51:01.710 --> 00:51:03.210
Brian Vanderwende: These easier, we can move things around.

303
00:51:20.010 --> 00:51:30.390
Siddhartha Ghosh: Okay, any other questions or topics that you would like to discuss will capture the discussion threads and put it under this in hug wiki.

304
00:51:32.040 --> 00:51:38.970
Siddhartha Ghosh: When we will share the meeting minutes in a mail to you will have links to the wiki.

305
00:51:39.990 --> 00:51:53.940
Siddhartha Ghosh: Particularly for university folks you need to use CIT password in order to get to our wiki if you are not familiar with it and current folks are already using the wiki so they know pretty much.

306
00:51:58.140 --> 00:52:06.750
Mick Coady: said the Charles Jackson asked a question, let you take it will there will there be topics for these meetings.

307
00:52:08.460 --> 00:52:11.520
Siddhartha Ghosh: And the topics are the agenda items is.

308
00:52:12.540 --> 00:52:13.350
Siddhartha Ghosh: Basically, up to.

309
00:52:13.440 --> 00:52:14.490
us to decide.

310
00:52:15.720 --> 00:52:25.830
Siddhartha Ghosh: Already we found few agent item, as I can see related to storage stuff and.

311
00:52:28.260 --> 00:52:37.740
Siddhartha Ghosh: you're also a follow up item I have not done from Jim the gpu data so probably We will report back after working with Jim.

312
00:52:38.520 --> 00:52:39.210
Brian Vanderwende: Exactly.

313
00:52:39.420 --> 00:52:52.650
Siddhartha Ghosh: What the requirements are and what the follow up decision or the discussion from our side, so no please pick up and that will be my suggestion to you not only.

314
00:52:53.460 --> 00:53:07.710
Siddhartha Ghosh: You can do it over here, but not necessarily not only here but, once you get the wiki link there you add your comment, create your page to voice your concerns or agent item for the next meeting.

315
00:53:08.580 --> 00:53:18.780
Siddhartha Ghosh: comment on topics we'll we'll try to correlate those things and form the agenda item for the next meeting when that's my preference at this point, thank you.

316
00:53:19.530 --> 00:53:30.540
Brian Vanderwende: I think you know a lot in those deployment groups will happen in one month, so perhaps bill and I are are some some assortment of folks can put together a.

317
00:53:31.500 --> 00:53:41.700
Brian Vanderwende: You know, a couple slides just as a starting point for the discussion on say the storage and how the gpus will be interact interacted with and things like that.

318
00:53:44.850 --> 00:53:54.150
Siddhartha Ghosh: Okay, and JEREMY has asked a question currently we have 328 100 gpus To begin with, how much your own.

319
00:53:55.200 --> 00:54:04.770
Siddhartha Ghosh: More more for assuming a need for expanding gpu partition with naacp three title lifetime and doubling well.

320
00:54:06.480 --> 00:54:10.710
Siddhartha Ghosh: At this point I would not rule that out the doubling.

321
00:54:12.030 --> 00:54:16.140
Siddhartha Ghosh: But it all depends on the issue, say, Jeremy.

322
00:54:18.330 --> 00:54:22.770
Siddhartha Ghosh: Quite frankly, this is our biggest worry when that is.

323
00:54:23.850 --> 00:54:34.770
Siddhartha Ghosh: The good use of this partition, that is the very reason we have this DDT or the gpu tiger team which are aggressively working with.

324
00:54:35.580 --> 00:54:53.190
Siddhartha Ghosh: You and others to come up with enough science cases to make this debut partisan busy for the time being, we do have our funds or do we will have funds are moving forward to expand gpu partitions.

325
00:55:02.190 --> 00:55:02.580
Mick Coady: and

326
00:55:03.630 --> 00:55:14.580
Mick Coady: said Dave just asked another good question of the 70 or more folks on the on this call about how many are from the university community.

327
00:55:16.110 --> 00:55:18.540
Mick Coady: I think he's concerned are they well represented.

328
00:55:19.170 --> 00:55:19.680
Mick Coady: So here.

329
00:55:20.100 --> 00:55:21.000
Mick Coady: You have those numbers.

330
00:55:23.430 --> 00:55:29.220
Siddhartha Ghosh: I do not know how many have giant adult so let me answer this, this is a good question.

331
00:55:30.810 --> 00:55:34.560
Siddhartha Ghosh: Obviously this, since this is by selection.

332
00:55:36.240 --> 00:55:48.450
Siddhartha Ghosh: I tried to come up with a criteria for selecting members out of this 3000 plus users, that we have, we cannot consider all of them, or all of you.

333
00:55:49.500 --> 00:56:03.570
Siddhartha Ghosh: Believe because that's on practical or impractical to manage, so I, we will have to select so the selection criteria we already mentioned in the web pages, but it will be nice to spell it out over here.

334
00:56:04.590 --> 00:56:20.280
Siddhartha Ghosh: We picked up all the nsc or majors jacuzzis like from an seo tip is there, anybody who has allocations for lot past two years, more than 5 million quarter hours on our system.

335
00:56:20.820 --> 00:56:32.490
Siddhartha Ghosh: The P eyes of all the nsc and jack we have considered or we have also considered any users who have spent more than 5 million quarter hours we're past two years.

336
00:56:33.000 --> 00:56:47.640
Siddhartha Ghosh: Then we tried to make it equitable the make enough participation for a wyoming folks because wyoming has a special allocation within our systems, right from the beginning, after we started this in wc.

337
00:56:48.690 --> 00:56:49.260
Siddhartha Ghosh: and

338
00:56:50.610 --> 00:57:06.180
Siddhartha Ghosh: With all this well folks from different a community as well as the developer folks like Dima doors and few others who are helping other users, they are not and themselves burning lot of cpu hours but helping other users to.

339
00:57:07.260 --> 00:57:14.640
Siddhartha Ghosh: or code or use our systems, so all this more folks together we have about.

340
00:57:15.750 --> 00:57:26.190
Siddhartha Ghosh: Close to 250 users total so that number is well represented within university and college and university of wyoming.

341
00:57:27.330 --> 00:57:48.390
Siddhartha Ghosh: Then we sent this invitation to all of these users, out of which we got back positive response from about 120 users incur a slightly more dominated over university, because in Korea this I responded more currently.

342
00:57:49.590 --> 00:58:08.070
Siddhartha Ghosh: Out of this hundred and 20 users you leave out about 90 is this from the support site and then or we have roughly 60 users from university in inca and about 40 users from the University.

343
00:58:10.080 --> 00:58:17.040
Siddhartha Ghosh: And this call about 110 or so are invited, I do not know how many have joined.

344
00:58:19.140 --> 00:58:34.320
Siddhartha Ghosh: And as we mentioned the criteria is pretty loose, we are not denying anybody from participating, rather we are inviting if you feel compelled to fill the represent a particular group particular usage particular model.

345
00:58:34.740 --> 00:58:41.820
Siddhartha Ghosh: We encourage you to spread this word out to your colleague, we can invite them.

346
00:58:43.560 --> 00:58:45.660
Siddhartha Ghosh: that's how the processes currently.

347
00:58:48.480 --> 00:58:59.880
Mick Coady: So they just call out right at 10 o'clock with I think a couple more questions we do you want to handle those and just.

348
00:59:01.380 --> 00:59:03.600
Siddhartha Ghosh: Okay, so let me quickly handle.

349
00:59:04.620 --> 00:59:05.010
Mick Coady: The one.

350
00:59:06.480 --> 00:59:17.820
Brian Vanderwende: Go ahead, I was gonna say there's one question from Eric about current gpu utilization and I see JEREMY pendant on this as well, I mean utilization is a is a.

351
00:59:18.480 --> 00:59:25.980
Brian Vanderwende: You know there's a couple different ways, you can define that but one important thing to keep in mind is the casper is more of a.

352
00:59:26.880 --> 00:59:33.480
Brian Vanderwende: test and development resource than a production resources for as far as the be 100 We certainly have codes that run there in a production sense.

353
00:59:34.290 --> 00:59:42.030
Brian Vanderwende: But we're really looking for people to use those be 100 gpus there to prepare themselves for the bigger resource that will come online next year.

354
00:59:43.110 --> 00:59:51.480
Brian Vanderwende: But in that sense, you know purely from scheduler availability, we see more time periods, where there's contention for those resources and a bit of a wait, then.

355
00:59:52.110 --> 01:00:07.260
Brian Vanderwende: Then they're running idle, but there is a there is a an up and down curve, since it is more, you know, since it does have a development aspect to it and and that's a bit of a fuzzy answer it's not a number but but I I think we're seeing.

356
01:00:09.090 --> 01:00:11.040
Brian Vanderwende: A good amount of interest on those resources.

357
01:00:12.240 --> 01:00:13.710
Mick Coady: yeah i'm sure that the.

358
01:00:15.150 --> 01:00:23.670
Mick Coady: All the conference in the world that the the gpu users will say that the contention is increased significantly lately.

359
01:00:29.460 --> 01:00:43.560
Siddhartha Ghosh: Okay, since we are a little over 10 so unless there is any burning question, I will prefer to aim to respect everybody's time here.

360
01:00:46.710 --> 01:01:01.080
Brian Vanderwende: And if you do have a question that you know, has you know, is more than a simple clever quick clarification question sending that to the email that could help us incorporated into the next.

361
01:01:02.280 --> 01:01:03.870
Brian Vanderwende: You know the following meetings as well.

362
01:01:08.280 --> 01:01:10.380
Siddhartha Ghosh: Okay, thank you, everybody.

363
01:01:11.250 --> 01:01:12.360
Siddhartha Ghosh: it's nice thing.

364
01:01:14.520 --> 01:01:19.440
Siddhartha Ghosh: and see you in a month that is next month six March, if I remember right the next meeting date.

